Reverse Proxy Status
Health metrics for the Traefik reverse proxy that terminates TLS and routes all traffic. Scanner API requests (/scanner/*) are load balanced across ingest nodes; all other traffic goes to the manager. Shows router, service, and middleware counts along with any warnings or errors.
Fields & Columns
| Name | Description |
|---|---|
| Routers | Total Traefik route rules that match incoming requests to backend services |
| Router Warnings | Configuration issues in routes that may affect routing but are not critical |
| Router Errors | Misconfigurations preventing routes from working correctly |
| Services | Total backend targets that handle matched requests (e.g., manager, ingest nodes) |
| Service Warnings | Issues with backend service definitions |
| Service Errors | Backend services that are misconfigured or unreachable |
| Middlewares | Total request/response transformations (headers, rate limiting, path stripping) |
| Middleware Warnings | Non-critical middleware configuration issues |
| Middleware Errors | Middleware misconfigurations blocking request processing |
Gotchas
- If Traefik is unavailable, both the GUI and scanner API are unreachable since all traffic routes through it.
- Warnings are non-critical but may cause subtle routing issues — review them before they escalate to errors.
- The environment badge (Development/Production) reflects the NODE_ENV of the manager, not Traefik itself.
API Calls (1)
| Method | Path | Description |
|---|---|---|
| GET | /api/health/infra/proxy-status | Fetch Traefik availability, environment, and component counts |