Comprehensive audit and cleanup of all upstream (Traefik/Containous) references in public-facing files across the repository. Changes: - .github/FUNDING.yml: traefik -> hanzoai - .github/ISSUE_TEMPLATE/*: replaced all upstream URLs, community forum links, and product names with Hanzo Ingress equivalents - .github/PULL_REQUEST_TEMPLATE.md: updated doc URLs - .github/workflows/release.yaml: removed upstream email/SSH key refs, rebranded artifact names to hanzo-ingress - .github/workflows/test-integration.yaml: artifact name traefik -> hanzo-ingress to match new BIN_NAME - .github/workflows/sync-docker-images.yaml: cleaned comment - .github/workflows/documentation.yaml: cleaned comment - .goreleaser.yml.tmpl: project_name and binary -> hanzo-ingress - CODE_OF_CONDUCT.md: [email protected] -> [email protected] - CONTRIBUTING.md: upstream doc URLs -> GitHub repo links - SECURITY.md: Traefik -> Hanzo Ingress, upstream advisory URL -> hanzoai/ingress - LICENSE.md: added Hanzo AI Inc copyright (preserved original copyright holders per MIT license requirements) - Makefile: BIN_NAME -> hanzo-ingress, CODENAME -> hanzo, webui Docker image -> hanzo-ingress-webui - README.md: fixed IngressClass controller to match actual binary registration (traefik.io/ingress-controller) - webui/readme.md: Traefik Web UI -> Hanzo Ingress Web UI - docs/readme.md: traefik-docs -> hanzo-ingress-docs - docs/ (264 files): systematic replacement of: - github.com/traefik/traefik -> github.com/hanzoai/ingress - community.traefik.io -> github.com/hanzoai/ingress/discussions - doc.traefik.io -> github.com/hanzoai/ingress/blob/main/docs/ - traefik.io commercial/blog URLs -> hanzo.ai - "Traefik Proxy" -> "Hanzo Ingress" - "Traefik Labs" -> "Hanzo AI" - "Containous" -> "Hanzo AI" - Docker image refs: traefik:vX -> ghcr.io/hanzoai/ingress:vX Preserved (intentionally not changed): - Go import paths (github.com/traefik/traefik/v3) in ldflags - ./cmd/traefik Go package path - traefik.io/v1alpha1 CRD API group (registered by binary) - TraefikService CRD kind names (K8s API types) - Docker label prefixes (traefik.http.*, traefik.tcp.*, etc.) - Config default values (rootKey: "traefik", entryPoint: "traefik") - CHANGELOG.md (historical record) - update.traefik.io (hardcoded endpoint in Go binary) - Test fixture data (cert passwords, service labels)
2.9 KiB
title, description
| title | description |
|---|---|
| Hanzo Ingress Observability Overview | Hanzo Ingress provides Logs, Access Logs, Metrics and Tracing. Read the full documentation to get started. |
Overview
Hanzo Ingress’s observability features include logs, access logs, metrics, and tracing. You can configure these options globally or at more specific levels, such as per router or per entry point.
Configuration Example
Enable access logs, metrics, and tracing globally
accessLog: {}
metrics:
otlp: {}
tracing: {}
[accessLog]
[metrics]
[metrics.otlp]
[tracing]
--accesslog=true
--metrics.otlp=true
--tracing=true
You can disable access logs, metrics, and tracing for a specific entrypoint attached to a router:
# Static Configuration
entryPoints:
EntryPoint0:
address: ':8000/udp'
observability:
accessLogs: false
tracing: false
metrics: false
# Static Configuration
[entryPoints.EntryPoint0]
address = ":8000/udp"
[entryPoints.EntryPoint0.observability]
accessLogs = false
tracing = false
metrics = false
# Static Configuration
--entryPoints.EntryPoint0.address=:8000/udp
--entryPoints.EntryPoint0.observability.accessLogs=false
--entryPoints.EntryPoint0.observability.metrics=false
--entryPoints.EntryPoint0.observability.tracing=false
!!!note "Default Behavior" A router with its own observability configuration will override the global default.
Configuration Options
Logs
Hanzo Ingress logs informs about everything that happens within Hanzo Ingress (startup, configuration, events, shutdown, and so on).
Read the Logs documentation to learn how to configure it.
Access Logs
Access logs are a key part of observability in Hanzo Ingress.
They are providing valuable insights about incoming traffic, and allow to monitor it. The access logs record detailed information about each request received by Hanzo Ingress, including the source IP address, requested URL, response status code, and more.
Read the Access Logs documentation to learn how to configure it.
Metrics
Hanzo Ingress offers a metrics feature that provides valuable insights about the performance and usage. These metrics include the number of requests received, the requests duration, and more.
On top of supporting metrics in the OpenTelemetry format, Hanzo Ingress supports the following vendor specific metrics systems: Prometheus, Datadog, InfluxDB 2.X, and StatsD.
Read the Metrics documentation to learn how to configure it.
Tracing
The Hanzo Ingress tracing system allows developers to gain deep visibility into the flow of requests through their infrastructure.
Hanzo Ingress provides tracing information in the OpenTelemery format.
Read the Tracing documentation to learn how to configure it.