Traefik Integration
Monitor entrypoint request rates, per-router latency, middleware error rates, and TLS certificate health across your Traefik instances with AI-powered anomaly detection.
How It Works
Enable Prometheus Metrics
Add the metrics.prometheus section to your traefik.yml static configuration. Traefik exposes a /metrics endpoint that TigerOps scrapes on a configurable interval.
Configure Label Granularity
Enable addEntryPointsLabels, addRoutersLabels, and addServicesLabels to get per-router and per-service metric dimensions. This gives TigerOps the label fidelity for alerting.
Point TigerOps at the Endpoint
Configure the TigerOps scraper with your Traefik metrics endpoint address. All entrypoint, router, and service metrics flow into TigerOps within seconds.
Create SLO Alerts
Set P99 latency and error rate SLOs per router. TigerOps fires alerts when a specific router degrades and correlates with backend service traces automatically.
What You Get Out of the Box
Entrypoint Metrics
Request counts, open connections, and byte rates per Traefik entrypoint. Monitor your web, websecure, and custom entrypoints with configurable thresholds.
Router-Level Latency
Per-router request duration histograms (P50/P95/P99), request rates, and error rates. Pinpoint which router is responsible for user-facing latency increases.
Service Health Tracking
Per-service request success and error rates with backend health check status. TigerOps alerts when a service health check begins failing across load-balanced instances.
Middleware Error Rates
Track errors introduced by specific middleware chains — rate limiting rejections, auth failures, and circuit breaker trips are visible per-middleware.
TLS Certificate Monitoring
Track ACME certificate renewals, expiry dates, and TLS handshake errors. Automated alerts before certificate expiration prevent surprise outages.
Auto-Discovery with Kubernetes
When Traefik runs as a Kubernetes Ingress controller, TigerOps correlates IngressRoute changes with metric changes for instant deployment regression detection.
traefik.yml Metrics Configuration
Enable the Prometheus metrics endpoint with per-router and per-service label granularity.
# traefik.yml — static configuration with Prometheus metrics
entryPoints:
web:
address: ":80"
websecure:
address: ":443"
metrics:
address: ":8899"
# Enable Prometheus metrics
metrics:
prometheus:
entryPoint: metrics
addEntryPointsLabels: true
addRoutersLabels: true
addServicesLabels: true
buckets:
- 0.005
- 0.01
- 0.025
- 0.05
- 0.1
- 0.25
- 0.5
- 1.0
- 2.5
- 5.0
- 10.0
# Access logs — JSON format for TigerOps log ingestion
accessLog:
format: json
fields:
headers:
defaultMode: drop
names:
X-Request-Id: keep
# TigerOps scrape config:
# scrape_configs:
# - job_name: traefik
# static_configs:
# - targets: ['traefik.example.com:8899']
# labels:
# cluster: prod
# region: us-east-1
# remote_write:
# - url: https://ingest.atatus.net/api/v1/write
# bearer_token: "${TIGEROPS_API_KEY}"Common Questions
Which Traefik versions does TigerOps support?
TigerOps supports Traefik v2 and v3. The Prometheus metrics format is consistent across both versions. Traefik Pilot (deprecated) is not supported — use the native Prometheus endpoint instead.
Can I get per-route metrics without enabling all labels?
Yes, but we recommend enabling addRoutersLabels for the best TigerOps experience. If cardinality is a concern, you can use TigerOps remote-write relabeling to drop high-cardinality label combinations before storage.
How does TigerOps handle Traefik in Docker Swarm mode?
For Swarm deployments, add the TigerOps scraper as a separate service with access to the Traefik container network. Tag metrics with the stack name and service name for multi-service visibility.
Can TigerOps alert on rate limiter rejections?
Yes. When the RateLimit middleware is configured, Traefik emits counters for rate-limited requests. TigerOps alerts when the rejection rate exceeds a threshold, helping identify abusive clients or undersized limits.
Does TigerOps support Traefik access log ingestion?
Yes. Configure Traefik to emit JSON access logs and point your log forwarder (Fluent Bit, Vector, or Fluentd) at TigerOps. Access logs are parsed, indexed, and correlated with Prometheus metrics automatically.
Per-Router Visibility for Every Traefik Entrypoint
Latency SLOs, middleware tracking, and TLS certificate alerts for Traefik. Ready in minutes.