DumbMonit
Monitorizar Hetzner Cloud com o DumbMonit
Servers, volumes and backups of a Hetzner Cloud project, read through the Hetzner Cloud API.
DocumentaçãoSite oficial: Hetzner Cloud
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 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).
Utilização típica. Servers, CPU, volumes, backups
Exemplos
- Hetzner Cloud project
Como se liga
O que precisa
- API tokenA read-only API token of the Hetzner Cloud project.
Portas de rede a abrir
443/TCPHetzner Cloud API (HTTPS, api.hetzner.cloud)
Passos de configuração: 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
Atenção. 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.