The Splunk Distribution of OpenTelemetry Collector deploys this integration as the
traefik monitor via the Smart Agent Receiver.
Traefik is an open-source HTTP reverse proxy and load balancer. Traefik exports Prometheus metrics that can be scraped by the SignalFx Smart Agent. These metrics can be categorized into Traefik-related, entrypoint-related, and backend-related metrics. Traefik-related metrics are prefixed by
process_. Entrypoint-related metrics are prefixed by
traefik_entrypoint_. Backend-related metrics are prefixed by
Traefik-related metrics are for monitoring Traefik itself. For instance, the
go_memstats_sys_bytes metric can be used to plot Traefik memory usage. Entrypoint- and backend-related 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.
See signalfx-agent/pkg/monitors/traefik/ for the monitor source.
This monitor requires signalfx-agent version 4.7.0 or later.
To install this integration:
Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform.
Configure the monitor, as described in the next section.
The Splunk Distribution of OpenTelemetry Collector allows embedding a Smart Agent monitor configuration in an associated Smart Agent Receiver instance.
Note: Providing a Traefik monitor entry in your Smart Agent or Collector configuration is required for its use. Use the appropriate form for your agent type.
Smart Agent 🔗
To activate this monitor in the Smart Agent, add the following to your agent configuration:
monitors: # All monitor config goes under this key - type: traefik ... # Additional config
See Smart Agent example configuration for an autogenerated example of a YAML configuration file, with default values where applicable.
Splunk Distribution of OpenTelemetry Collector 🔗
To activate this monitor in the OpenTelemetry Collector, add the following to your agent configuration:
receivers: smartagent/traefik: type: traefik ... # Additional config
To complete the monitor activation, you must also include the
smartagent/traefik receiver item in a
metrics pipeline. To do this, add the receiver item to the
receivers section of your configuration file.
See configuration examples for specific use cases that show how the collector can integrate and complement existing environments.
Configuration settings 🔗
The following table shows the configuration options for the
||Host of the exporter|
||Port of the exporter|
||HTTP timeout duration for both read and writes. This should be a duration string that is accepted by func ParseDuration (default:
||Basic Auth username to use on each request, if any.|
||Basic Auth password to use on each request, if any.|
||A map of HTTP header names to values. Comma separated multiple values for the same message-header is supported.|
||If useHTTPS is
||Path to the CA cert that has signed the TLS cert, unnecessary if
||Path to the client TLS cert to use for TLS required connections|
||Path to the client TLS key to use for TLS required connections|
||Use pod service account to authenticate. (default:
||Path to the metrics endpoint on the exporter server, usually
||Send all the metrics that come out of the Prometheus exporter without any filtering. This option has no effect when using the prometheus exporter monitor directly since there is no built-in filtering, only when embedding it in other monitors. (default:
The Smart Agent must have network access to Traefik.
For deployment-specific configuration instructions, see deployments.
The following is an example configuration that shows:
traefikmonitor can be configured to scrape Prometheus metrics in the default path
/metricson port 8080
traefikmonitor can be configured to add dimension
metric_source=traefikto the metrics and export them to Splunk Observability Cloud
monitors: - type: traefik discoveryRule: port == 8080 extraDimensions: metric_source: traefik
Traefik configuration 🔗
Edit the Traefik configuration file, typically
traefik.toml, to enable Traefik to expose Prometheus metrics at an
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. For example,
./traefik -c traefik.toml
However, when running the Traefik Docker image, the configuration file is mounted to 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 Traefik configuration file is not available, use the sample configuration file to get started.
For more information, see Traefik documentation.
These are the metrics available for this integration.