Integration · Databases
PostgreSQL
pg_stat_*, replication lag, connection pool, autovacuum.
What gets collected
A connection string with a read-only user. Metrics: WAL throughput, replication lag, slow queries (with a configurable threshold), bloat estimate, active connections per database.
Requirements
- ✓PostgreSQL 12+
- ✓role with pg_monitor
- ✓pg_stat_statements
- ✓read-only connection
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
pg.connections.activepg.replication.lagpg.wal.throughputpg.slow_queriespg.bloat.estimatepg.deadlocksSetup steps
- 1
CREATE USER unimoni WITH PASSWORD ... LOGIN - 2
GRANT pg_monitor TO unimoni - 3pg_stat_statements in shared_preload_libraries
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
PostgreSQL
Frequently asked questions
- What does Unimoni collect from PostgreSQL?
- pg_stat_*, replication lag, connection pool, autovacuum. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across PostgreSQL and everything else in one place.
- How long does it take to connect PostgreSQL?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the PostgreSQL integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is PostgreSQL monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.