Troubleshoot Traefik

When to use this skill

• Any time the user reports a Traefik service behaving outside its expected envelope (elevated errors, latency, saturation, resource exhaustion, or unexpected restarts).
• An on-call engineer is paging on a Netdata alert tied to a Traefik instance and wants a structured triage path.

Key facts

• This skill wraps the Netdata operator playbook for Traefik. It does not replace the playbook; it routes a coding agent through MCP queries against the same signals the playbook relies on.
• Netdata observes the signals listed in the rule files via its native collectors, plus any OpenTelemetry-shipped metrics that your Traefik instrumentation adds. Both paths end at the same MCP query surface.
• Netdata's traefik collector emits 3 context(s) under traefik.*. The rule files enumerate which contexts surface which domain; the Verification section below names the load-bearing ones explicitly.