design
Turning PostgreSQL CSV Logs into Durable Metrics
The product boundary, durable-state protocol, bounded metric contract, and failure semantics for PostgreSQL CSV log metrics in PG Exporter
Caching pgBackRest Metrics Outside the Scrape Path
Why PG Exporter executes pgBackRest in a bounded background worker and serves an immutable last-good snapshot
The PostgreSQL Observability Product We Chose Not to Build
Why a local-first PostgreSQL incident workbench was explored, then replaced by a much smaller CSV-log metrics feature inside PG Exporter
One Endpoint, Several Sources: The Composite Exporter Contract
How PG Exporter combines PostgreSQL, PgBouncer, Patroni, and cached components without weakening the primary PostgreSQL scrape
Snapshot Histograms Are Gauges, Not Counters
Why PG Exporter rebuilds SQL distributions on every query and exposes their buckets, count, and sum as gauge series