DumbMonit
Monitorizar Hetzner Cloud con DumbMonit
Servers, volumes and backups of a Hetzner Cloud project, read through the Hetzner Cloud API.
DocumentaciónSitio web oficial: Hetzner Cloud
Las descripciones están en inglés, como en el producto. Las etiquetas de la página siguen su idioma.
Qué vigila DumbMonit
The servers of a Hetzner Cloud project through the Hetzner Cloud API: servers that are not running, a processor that stays saturated, backups that stopped and volumes attached to nothing. DumbMonit reads the API at api.hetzner.cloud/v1 once a minute with a read-only project token sent as a bearer token. The list of servers is required; the activity of the servers, the volumes and the backups are optional parts that, if refused, are skipped without making the monitor fail. One monitor reads one project (a token belongs to a single project).
Uso habitual. Servers, CPU, volumes, backups
Ejemplos
- Hetzner Cloud project
Cómo se conecta
Qué necesita
- API tokenA read-only API token of the Hetzner Cloud project.
Puertos de red que abrir
443/TCPHetzner Cloud API (HTTPS, api.hetzner.cloud)
Pasos de configuración: Create a read-only API token for DumbMonit
In the Hetzner Cloud Console, open the project to monitor, then Security > API tokens > Generate API token.
Name it DumbMonit and choose the Read permission (not Read & Write).
Click Generate API token, then copy the token: it is shown once.
In DumbMonit, use this address and paste the token as API token. One monitor reads one project.
api.hetzner.cloud
Ojo. A server that is powered off is reported as not running, on purpose or not: mute the rule for it if that is expected. The API allows 3600 requests per hour and project, so server metrics are read for 10 servers by default.