DumbMonit
ИнтеграцииБазы данных и очереди сообщений
Мониторинг PostgreSQL database в 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.
ДокументацияОфициальный сайт: PostgreSQL
Описания на английском, как в самом продукте. Подписи на странице — на вашем языке.
Что проверяет DumbMonit
Типичное применение. Database: connection and a query you choose
Примеры
- The database behind Nextcloud or Immich
- A Home Assistant recorder
- An application database
- A TimescaleDB instance
Как подключается
Что понадобится
- Username / passwordA read-only account created for monitoring, never an application one.
Порт по умолчанию: 5432
Шаги настройки: 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;
Обратите внимание. The check opens a real connection on every poll: on an instance close to its connection limit, give it a longer interval.