DumbMonit
IntegrazioniDatabase e messaggistica
Monitorare PostgreSQL database con DumbMonit
Logs in, runs a query and reads the server's health: catches a database that is up but no longer answering, and one that is running out of connections, lagging or bloating.
DocumentazioneSito ufficiale: PostgreSQL
Le descrizioni sono in inglese, come nel prodotto. Le etichette della pagina seguono la tua lingua.
Cosa controlla DumbMonit
Uso tipico. Database: connection and a query you choose
Esempi
- The database behind Nextcloud or Immich
- A Home Assistant recorder
- An application database
- A TimescaleDB instance
Come si collega
Cosa serve
- Username / passwordA read-only account created for monitoring, never an application one.
Porta predefinita: 5432
Passaggi di configurazione: Monitor a PostgreSQL database
In psql, create a role that may only log in.
CREATE ROLE dumbmonit LOGIN PASSWORD 'a-long-password';Allow it to connect from the DumbMonit host with this line in pg_hba.conf (adjust the address), then reload PostgreSQL.
host all dumbmonit 10.0.0.5/32 scram-sha-256In DumbMonit, enter the server, for example db.home.lan:5433 (port 5432 by default), then the role's user and password.
Optional: replace the default query SELECT 1 with one that returns a single number, to chart it.
Optional, for the complete server health metrics (sessions of every user, locks, replication, vacuum): let the role read the statistics views.
GRANT pg_monitor TO dumbmonit;
Attenzione. The check opens a real connection on every poll: on an instance close to its connection limit, give it a longer interval.