Traefik 🔗

The Splunk Distribution of the OpenTelemetry Collector uses the Smart Agent receiver with the traefik monitor type to collect metrics from Traefik.

This monitor is available on Kubernetes, Linux, and Windows.

Benefits 🔗

After you configure the integration, you can access these features:

View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Splunk Observability Cloud.
View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Use navigators in Splunk Infrastructure Monitoring.
Access the Metric Finder and search for metrics sent by the monitor. For information, see Search the Metric Finder and Metadata Catalog.

Installation 🔗

Follow these steps to deploy this integration:

Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:
Configure the integration, as described in the Configuration section.
Restart the Splunk Distribution of the OpenTelemetry Collector.

Configuration 🔗

To use this integration of a Smart Agent monitor with the Collector:

Include the Smart Agent receiver in your configuration file.
Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

See how to Use Smart Agent monitors with the Collector.
See how to set up the Smart Agent receiver.
For a list of common configuration options, refer to Common configuration settings for monitors.
Learn more about the Collector at Get started: Understand and use the Collector.

Example 🔗

To activate this integration, add the following to your Collector configuration:

receivers:
  smartagent/traefik:
    type: traefik
    ...  # Additional config

Next, add the monitor to the service.pipelines.metrics.receivers section of your configuration file:

service:
  pipelines:
    metrics:
      receivers: [smartagent/traefik]

Configuration settings 🔗

The following table shows the configuration options for the traefik monitor:

Option	Required	Type	Description
`httpTimeout`	No	`int64`	HTTP timeout duration for both reads and writes. Must be a duration string accepted by `ParseDuration`. Default value is `10s`.
`username`	No	`string`	Username to use on each request.
`password`	No	`string`	Password to use on each request.
`useHTTPS`	No	`bool`	If true, the agent connects to the server using HTTPS instead of plain HTTP. Default value is `false`.
`httpHeaders`	No	`map of strings`	A map of HTTP header names to values. Comma-separated multiple values for the same message-header are supported.
`skipVerify`	No	`bool`	If both `useHTTPS` and `skipVerify` are `true`, the TLS certificate of the exporter is not verified. Default value is `false`.
`caCertPath`	No	`string`	Path to the CA certificate that has signed the TLS certificate, unnecessary if `skipVerify` is set to false.
`clientCertPath`	No	`string`	Path to the client TLS certificate to use for TLS required connections.
`clientKeyPath`	No	`string`	Path to the client TLS key to use for TLS required connections.
`host`	Yes	`string`	Host of the exporter.
`port`	Yes	`integer`	Port of the exporter.
`useServiceAccount`	No	`bool`	Use pod service account to authenticate. Default value is `false`.
`metricPath`	No	`string`	Path to the metrics endpoint on the exporter server. The default value is `/metrics`.
`sendAllMetrics`	No	`bool`	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. Default value is `false`.

The Collector or Smart Agent must have network access to Traefik.

Traefik configuration 🔗

Edit the Traefik configuration file, for example traefik.toml, to activate Traefik to expose Prometheus metrics at an endpoint. By default, the endpoint is on path /metrics. When running the Traefik binary, pass the path to the configuration file using the -c argument. For example, ./traefik -c traefik.toml.

When running the Traefik Docker image, use the /etc/traefik/traefik.toml volume. 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 the Traefik documentation.

Metrics 🔗

Traefik exports Prometheus metrics which can be categorized into Traefik, entrypoint, and back-end metrics.

Traefik-related metrics are for monitoring Traefik itself and are prefixed by go_ and process_. For instance, the go_memstats_sys_bytes metric can be used to plot Traefik memory usage.
Entrypoint and back-end metrics are the number and duration of requests measured at entrypoints and back ends. Entrypoint-related metrics are prefixed by traefik_entrypoint_. Backend-related metrics are prefixed by traefik_backend_.

The following table shows the metrics that are available for this integration:

Notes 🔗

To learn more about the available in Splunk Observability Cloud see Metric types
In host-based subscription plans, default metrics are those metrics included in host-based subscriptions in Splunk Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See Metric categories for more information.
In MTS-based subscription plans, all metrics are custom.
To add additional metrics, see how to configure extraMetrics in Add additional metrics

Troubleshooting 🔗

If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.

Available to Splunk Observability Cloud customers

Submit a case in the Splunk Support Portal .
Contact Splunk Support .

Available to prospective customers and free trial users

Ask a question and get answers through community support at Splunk Answers .
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.

This page was last updated on Feb 11, 2025.

Related Topics