Pro plan from £5 per endpoint per month · see pricing
Secronyx
AvailableLinuxWindowsmacOS

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.

What it answers

Questions an on-call engineer asks, which an AI client can answer with this integration.

  • 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 integration'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

Integration
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, configure 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 that comes with it. secronyx integration setup traefik prints it; an administrator applies it by hand.

# The least privilege for the traefik integration: Traefik's API on an internal # entrypoint that only this host reaches. The API has no users or roles, # so nothing can say how powerful a login is: every client that reaches # it can read the whole routing config (routers and their rules, services # and their server URLs, middleware settings with basic-auth hashes and # header values, TLS options). It has no write endpoints of its own; the # REST provider (providers.rest) adds one that replaces the routing # config, so leave that off. The integration only sends GETs to /api/overview, # /api/http/routers and /api/http/services (the engine refuses every other # path and method for driver traefik). # # 1. Static config (traefik.yml): an entrypoint on loopback for the API. # api.insecure serves the API without a login on the "traefik" # entrypoint, so bind that entrypoint to 127.0.0.1 too: entryPoints: traefik: address: "127.0.0.1:8080" api: insecure: true # Then configure with auth none (the default endpoint is localhost:8080): # secronyx integration configure traefik # # 2. Or, with a login: api.insecure off, a loopback entrypoint, and a # router to the API behind basic auth in the dynamic config. Make the # hash with: htpasswd -nb {{user}} '<password>' # # entryPoints: # internal: # address: "127.0.0.1:8082" # api: {} # # http: # routers: # secronyx-api: # entryPoints: [internal] # rule: PathPrefix(`/api`) # service: api@internal # middlewares: [secronyx-api-auth] # middlewares: # secronyx-api-auth: # basicAuth: # users: ["{{user}}:<hash>"] # # and configure with: secronyx integration configure traefik --auth password # --user {{user}} --password-stdin --endpoint 127.0.0.1:8082 # --allow-unchecked-privilege # # Do not publish the API on an entrypoint other hosts reach (the dashboard # and the API share the same handler): every client that reaches it reads # the whole routing config.

See it run

Recording coming. Configure, setup and status runs for this integration 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 integration 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 integration can read whatever its login can see.