DumbMonit
IntégrationsSites web et serveurs web
Surveiller Traefik avec DumbMonit
The reverse proxy: routers disabled by a configuration error, backend servers failing their health check, certificates that never arrive or are not renewed, and the share of 5xx answers.
DocumentationSite officiel : Traefik
Les descriptions des produits sont en anglais, comme dans le produit. Les libellés de la page suivent votre langue.
Ce que DumbMonit surveille
The reverse proxy: routers disabled by a configuration error, backend servers failing their health check, certificates that a resolver never obtained or that are not renewed, and the share of 5xx answers.
Usage typique. Reverse proxy: disabled routers, backend servers down, certificates not obtained or not renewed, 5xx share
Exemples
- Traefik in Docker
- Traefik on Kubernetes
- Traefik in front of self-hosted apps
Comment il se connecte
Ce qu'il faut
- basicAuth userThe user of the basicAuth middleware in front of the API and the metrics.
Aucun compte nécessaire.
Ports réseau à ouvrir
8080/TCPAPI and metrics (HTTP, default)
Étapes de mise en place: Let DumbMonit read Traefik's API
Add these arguments to Traefik's command (or the same keys to its static configuration), then restart it.
--api.insecure=true --metrics.prometheus=trueOpen http://traefik.lan:8080/api/overview from the DumbMonit host: it must answer with JSON.
Optional: protect /api and /metrics with a basicAuth middleware on an entry point of your own, and create the user with htpasswd.
htpasswd -nbB dumbmonit 'a-long-password'In DumbMonit, enter the Traefik host, for example traefik.lan, with the port of that entry point if it is not 8080.
À savoir. Port 8080 answers without a password: filter it so that only the DumbMonit host reaches it.