Files
zeekayandHanzo Dev 15d100931d
Hanzo CI/CD / cicd (push) Failing after 9m46s
CI/CD / cicd (push) Failing after 10m4s
Name the ingress in the docs, and fix what that exposed
Most of it was stale, not cosmetic: the docs taught `TRAEFIK_*` env,
`traefik.http.*` labels, `traefik.ingress.kubernetes.io/` annotations,
`.traefik.yml` plugins and `traefik_*` metrics. This binary answers to
`INGRESS_*`, `ingress.http.*`, `ingress.kubernetes.io/`, `.ingress.yml` and
`ingress.*` — a reader following the old text configured nothing.

Two were worse than stale. Gateway API examples gave `group: traefik.io` for an
IngressService backendRef, which kubernetes.go:1265 refuses against hanzo.ai.
The contributing guide built with `github.com/traefik/ingress` ldflags against
a module that is `github.com/hanzoai/ingress/v3`.

script/code-gen.sh globs `hanzo.ai_*.yaml` and matched nothing — the per-CRD
dumps had been deleted and never regenerated, so `cat` failed the script under
`set -e`. controller-gen v0.19.0 restores all ten; they concatenate
byte-for-byte into the committed definition and fixture.

CHANGELOG.md is untouched: 6,789 lines of imported release history, where a
rewrite would falsify the record rather than rebrand it. `@traefiklabs/faency`,
`traefik/whoami`, k3s's `--disable=traefik`, the `traefik.io` CRD group and the
MIT attribution stay — upstream's addresses, not our brand.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-16 13:01:19 -07:00

2.7 KiB

title, description
title description
Hanzo Ingress Datadog Metrics Documentation Hanzo Ingress supports Datadog for backend metrics. Read the technical documentation to enable Datadog for observability.

Datadog

To enable the Datadog:

metrics:
  datadog: {}
[metrics]
  [metrics.datadog]
--metrics.datadog=true

address

Required, Default="127.0.0.1:8125"

Address instructs exporter to send metrics to datadog-agent at this address.

This address can be a Unix Domain Socket (UDS) in the following format: unix:///path/to/datadog.socket. When the prefix is set to unix, the socket type will be automatically determined. To explicitly define the socket type and avoid automatic detection, you can use the prefixes unixgram for SOCK_DGRAM (datagram sockets) and unixstream for SOCK_STREAM (stream sockets), respectively.

metrics:
  datadog:
    address: 127.0.0.1:8125
[metrics]
  [metrics.datadog]
    address = "127.0.0.1:8125"
--metrics.datadog.address=127.0.0.1:8125

addEntryPointsLabels

Optional, Default=true

Enable metrics on entry points.

metrics:
  datadog:
    addEntryPointsLabels: true
[metrics]
  [metrics.datadog]
    addEntryPointsLabels = true
--metrics.datadog.addEntryPointsLabels=true

addRoutersLabels

Optional, Default=false

Enable metrics on routers.

[metrics]
  [metrics.datadog]
    addRoutersLabels = true
metrics:
  datadog:
    addRoutersLabels: true
--metrics.datadog.addrouterslabels=true

addServicesLabels

Optional, Default=true

Enable metrics on services.

metrics:
  datadog:
    addServicesLabels: true
[metrics]
  [metrics.datadog]
    addServicesLabels = true
--metrics.datadog.addServicesLabels=true

pushInterval

Optional, Default=10s

The interval used by the exporter to push metrics to datadog-agent.

metrics:
  datadog:
    pushInterval: 10s
[metrics]
  [metrics.datadog]
    pushInterval = "10s"
--metrics.datadog.pushInterval=10s

prefix

Optional, Default="ingress"

The prefix to use for metrics collection.

metrics:
  datadog:
    prefix: ingress
[metrics]
  [metrics.datadog]
    prefix = "ingress"
--metrics.datadog.prefix=ingress