monitoring: add postgres_exporter and Postgres alert rules #459

Nytt ärende

Öppen

öppnade 2026-09-08 23:04:25 +00:00 av supernaut · 0 kommentarer

supernaut kommenterad

2026-09-08 23:04:25 +00:00

Ägare

Postgres holds both product databases (Forgejo and the portal). Monitoring today only knows whether the unit is active. Connection exhaustion, bloat, replication or slow queries produce no signal.

Add postgres_exporter as a Quadlet unit in monitoring-agent (same hardening and memory shape as node-exporter), a read-only monitoring role in Postgres created by the postgres role, a scrape job in vmagent-scrape.yml.j2, and rules for: exporter down, connections above 80 % of max_connections, oldest transaction age, database size growth, and a staleness rule for the exporter itself.

Postgres holds both product databases (Forgejo and the portal). Monitoring today only knows whether the unit is active. Connection exhaustion, bloat, replication or slow queries produce no signal. Add `postgres_exporter` as a Quadlet unit in `monitoring-agent` (same hardening and memory shape as `node-exporter`), a read-only monitoring role in Postgres created by the `postgres` role, a scrape job in `vmagent-scrape.yml.j2`, and rules for: exporter down, connections above 80 % of `max_connections`, oldest transaction age, database size growth, and a staleness rule for the exporter itself.

supernaut lade till detta till projektet Bitborg Infrastructure

2026-09-08 23:04:46 +00:00

supernaut lade till etiketterna

2026-09-08 23:05:23 +00:00

Logga in för att delta i denna konversation.