Skip to main content

Traefik monitoring with Netdata

Traefik is a leading modern reverse proxy and load balancer that makes deploying microservices easy. .

This module will monitor one or more Traefik instances, depending on your configuration.

Requirements#

Charts#

Current implementation collects only entrypoint metrics.

Entrypoint#

  • Processed HTTP requests, partitioned by code class in requests/s
  • Average HTTP request processing time, partitioned by code class in milliseconds
  • Open connections, partitioned by method in connections

Configuration#

Edit the go.d/traefik.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/traefik.conf

Needs only url to server's /metrics endpoint. Here is an example for 2 servers:

jobs:
- name: local
url: http://127.0.0.1:8082/metrics
- name: remote
url: http://203.0.113.10:8082/metrics

For all available options please see module configuration file.

Troubleshooting#

To troubleshoot issues with the traefik collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

  • First, navigate to your plugins directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the setting plugins directory. Once you're in the plugin's directory, switch to the netdata user.
cd /usr/libexec/netdata/plugins.d/
sudo -u netdata -s
  • You can now run the go.d.plugin to debug the collector:
./go.d.plugin -d -m traefik

Reach out

If you need help after reading this doc, search our community forum for an answer. There's a good chance someone else has already found a solution to the same issue.

Documentation

Community

Last updated on