Traefik
See whether Traefik has routers or services in error, why a router is disabled, which router serves a host, and which backend servers its health checks mark down, from its API on this host with read-only requests. This plugin is in the next Secronyx release; the current download does not include it yet.
What it answers
Questions an on-call engineer asks, which an AI client can answer with this plugin.
- Are any Traefik routers or services in error after the last config change?
- Why does this site return 404 through Traefik, and which router should match it?
- Which backend servers do Traefik's health checks mark down?
- Which middlewares and TLS options does this router use?
- Which configuration providers does Traefik use, and is the access log on?
What it returns
Each of the plugin's read-only tools, described in words.
- Traefik routing overview in one row - HTTP, TCP and UDP routers, services and middlewares with how many are in error or warning, the configuration providers, metrics, tracing and access log
- Traefik HTTP routers with their rule, entry points, service, middlewares, priority and TLS settings, status (enabled, warning or disabled) and the errors that disabled them
- Traefik HTTP services with their type, status, the routers that use them, their backend servers and whether each server is up or down, the health check path and the errors Traefik reports
At a glance
- Plugin
- traefik 1.0.0
- Publisher
- levantar
- Platforms
- Linux, Windows, macOS
Tested on
- Traefik 3.1.7 and 3.7.17 on Linux (Ubuntu, Docker), GitHub Actions
- Traefik 3.1.7 on macOS (official release), GitHub Actions
- Traefik 3.1.7 on Windows Server (official release), GitHub Actions
How it logs in
Without an explicit choice, install tries the methods that need no secret first, in this order.
- No login (a local endpoint)
- A user name and password
The least-privilege login
The setup file in the pack. secronyx plugin setup traefik prints it; an administrator applies it by hand.
See it run
Recording coming. Install, setup and status runs for this plugin are recorded on the shared test lab, and appear here once they have run.
Read-only, in layers
Every request is a GET or HEAD to the endpoint the operator configured, on a path fixed in the signed pack. Redirects are not followed, and requests known to change state are refused.
These controls narrow what the plugin can do; none of them is a guarantee on its own. An administrator can still accept a more powerful login on purpose (audited and shown in status), root or Administrator on the host can replace the agent, and the plugin can read whatever its login can see.