DumbMonit

IntegraçõesSites e servidores web

Monitorizar Traefik com o 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.

DocumentaçãoSite oficial: Traefik

As descrições estão em inglês, como no produto. Os rótulos da página seguem o seu idioma.

O que o DumbMonit vigia

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.

Utilização típica. Reverse proxy: disabled routers, backend servers down, certificates not obtained or not renewed, 5xx share

Exemplos

  • Traefik in Docker
  • Traefik on Kubernetes
  • Traefik in front of self-hosted apps

Como se liga

O que precisa

  • basicAuth userThe user of the basicAuth middleware in front of the API and the metrics.

Não é preciso nenhuma conta.

Portas de rede a abrir

  • 8080/TCPAPI and metrics (HTTP, default)
Passos de configuração: Let DumbMonit read Traefik's API
  1. Add these arguments to Traefik's command (or the same keys to its static configuration), then restart it.

    --api.insecure=true
    --metrics.prometheus=true
  2. Open http://traefik.lan:8080/api/overview from the DumbMonit host: it must answer with JSON.

  3. 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'
  4. In DumbMonit, enter the Traefik host, for example traefik.lan, with the port of that entry point if it is not 8080.

Atenção. Port 8080 answers without a password: filter it so that only the DumbMonit host reaches it.