Docs » Integrations Guide » Integrations Reference » Traefik

../../_images/integration_traefik.png Traefik 🔗


Configure Traefik to expose internal metrics as prometheus metrics at an endpoint. Install the SignalFx Smart Agent and configure it to access SignalFx and use the prometheus-exporter monitor.


Software Version
signalfx-agent 3.4+


Follow these steps to install this plugin:

  1. Install the SignalFx Smart Agent in your environment.
  2. Modify the Smart Agent configuration file as described in Smart Agent Configuration, below.
  3. Configure Traefik to expose Prometheus metrics endpoint as described in Traefik Configuration, below.


Traefik Configuration 🔗

Edit the Traefik configuration file, typically traefik.toml, to enable Traefik to expose prometheus metrics at endpoint. The endpoint is on path /metrics by default. When running the Traefik binary, the configuration file is typically passed in as a command line argument.

./traefik -c traefik.toml

However, when running the Traefik Docker image, the configuration file is mounted to the volume /etc/traefik/traefik.toml. For example,

docker run -d -p 8080:8080 -p 80:80 -v $PWD/traefik.toml:/etc/traefik/traefik.toml

If the configuration file is not available use the sample configuration file. The Smart Agent must have network access to Traefik. This means for instance that, in a Docker environment, the Smart Agent container needs to share a network with the Traefik container. So the Docker run command to start the agent may look as follows:

Before we can send metrics to SignalFx, we need to make sure you are sending them to the correct SignalFx realm. To determine what realm you are in (YOUR_SIGNALFX_REALM), check your profile page in the SignalFx web application (click the avatar in the upper right and click My Profile). If you are not in the us0 realm, you will need to set the URL configuration option below to use the correct realm, as shown below.

You will also need to set the SFX_ACCESS_TOKEN configuration option to your SignalFx organization access token (YOUR_SIGNALFX_API_TOKEN). For more information on authentication, see the API’s Authentication documentation.

docker run --rm \
-v /var/run/docker.sock:/var/run/docker.sock \
-v <agent.yaml path>:/etc/signalfx/agent.yaml \
--net <traefik container network> \<version>

Smart Agent Configuration 🔗

Find and edit the Smart Agent configuration file agent.yaml to enable the Docker observer and configure the prometheus-exporter monitor as described here. For example, the configuration below will cause the Smart Agent to query the Docker Engine API for all running containers with port 8080 exposed and export Prometheus metrics from endpoint <container ip>:8080/metrics.

  - type: docker
  - type: prometheus-exporter
    discoveryRule: port == 8080
    metric_source: traefik

Also, metrics can be excluded by configuring the metricsToExclude section of the Smart Agent configuration file.


The Smart Agent exports Prometheus metrics exposed by Traefik. These metrics can be categorized into Traefik-related, entrypoint-related and backend-related metrics. The Traefik-related metrics are prefixed by go_ and process_. The entrypoint-related metrics are prefixed by traefik_entrypoint_ and the backend-related metrics prefixed by traefik_backend_.

The Traefik-related metrics are for monitoring Traefik itself. For instance, the go_memstats_sys_bytes metric can be used to plot Traefik memory usage. The entrypoint-related and backend-related key metrics are the number and duration of requests measured at entrypoints and backends. These metrics are used to compute measurements such as the average request duration.

../../_images/traefik_overview.pngOverview ../../_images/traefik_entrypoints.pngEntryPoints ../../_images/traefik_backends.pngBackends

The entrypoint-related and backend-related metrics also include metrics for the number of entrypoints connections, backends connections and backend server up/down flag.