Traefik Observability


In this tutorial, we will see how to export metrics and traces of Traefik to SigNoz. Visualizing Traefik metrics and traces will help you to understand the performance of services running behind Traefik and troubleshoot issues.


  • Traefik v3.0 or above
  • Must have SigNoz running. You can follow the installation guide to install SigNoz.
  • Must have SigNoz OtelCollector accessible from Traefik
  • If you don’t already have a SigNoz Cloud account, you can sign up here.

Export Traefik Metrics and Traces to SigNoz

Based on how you are running SigNoz (e.g. SigNoz Cloud, in an independent VM or Kubernetes cluster), you have to provide the address to send data from the above receivers.

In this section, we will see how to export Traefik metrics and traces to SigNoz Cloud.

For metrics, we will have to set the following CLI flags in Traefik:

  • --metrics.openTelemetry=true
  • --metrics.openTelemetry.grpc=true
  • --metrics.openTelemetry.address=ingest.{region}
  • --metrics.openTelemetry.insecure=false
  • --metrics.openTelemetry.headers.signoz-access-token=SIGNOZ_INGESTION_KEY

For traces, we will have to set the following CLI flags in Traefik:

  • --tracing.openTelemetry=true
  • --tracing.openTelemetry.grpc=true
  • --tracing.openTelemetry.address=ingest.{region}
  • --tracing.openTelemetry.insecure=false
  • --tracing.openTelemetry.headers.signoz-access-token=SIGNOZ_INGESTION_KEY

We will take an example docker-compose.yaml with a simple hello-app running behind Traefik.

# docker-compose.yaml {13-14,18-19}

version: '3'
    image: traefik:v3.0.0-beta3
      - signoz:host-gateway
      - --api.insecure=true
      - --providers.docker
      - --metrics.openTelemetry=true
      - --metrics.openTelemetry.grpc=true
      - --metrics.openTelemetry.insecure=false
      - --metrics.openTelemetry.address=ingest.{region}
      - --metrics.openTelemetry.headers.signoz-access-token=SIGNOZ_INGESTION_KEY
      - --tracing.openTelemetry=true
      - --tracing.openTelemetry.grpc=true
      - --tracing.openTelemetry.insecure=false
      - --tracing.openTelemetry.address=ingest.{region}
      - --tracing.openTelemetry.headers.signoz-access-token=SIGNOZ_INGESTION_KEY
      - "80:80"
      - "8080:8080"
      - /var/run/docker.sock:/var/run/docker.sock
      - PORT=8080
      traefik.enable: true
      traefik.http.routers.hello-app.rule: Host(`hello-app.docker.localhost`)
      traefik.http.routers.hello-app.entrypoints: http
      traefik.http.routers.hello-app.service: hello-app
πŸ“ Note
  • Replace SIGNOZ_INGESTION_KEY with the one provided by SigNoz.
  • Replace {region} with the region of your SigNoz Cloud instance.

Refer to the table below for the region-specific endpoints:


To start the services, run the following command:

docker compose up -d

We will visit the hello-app service to generate some traffic.

curl -H Host:hello-app.docker.localhost

Now, we will visit the SigNoz UI to see the traces and metrics.

Traefik Traces

To plot metrics generated from Traefik, follow the instructions given in the docs here.

Check out the List of metrics from Traefik.

List of Metrics

Traefik Metrics

  • traefik_config_last_reload_success
  • traefik_config_reloads_total
  • traefik_entrypoint_request_duration_seconds_bucket
  • traefik_entrypoint_request_duration_seconds_count
  • traefik_entrypoint_request_duration_seconds_sum
  • traefik_entrypoint_requests_bytes_total
  • traefik_entrypoint_requests_total
  • traefik_entrypoint_responses_bytes_total
  • traefik_open_connections
  • traefik_service_request_duration_seconds_bucket
  • traefik_service_request_duration_seconds_count
  • traefik_service_request_duration_seconds_sum
  • traefik_service_requests_bytes_total
  • traefik_service_requests_total
  • traefik_service_responses_bytes_total