What I learned creating Postgres monitoring metrics for Citus on Azure
summary
Practical guide to Hyperscale (Citus) monitoring on Azure: recommends exporting constant, tagged metrics at a tunable granularity and alerting disk at ~90% before outages; use pg_stat_statements and pg_stat_activity to find long queries and connection leaks; monitor WAL size and replication slots to explain sudden disk growth; watch IO, cache/committed/dirty memory, and summarize log error types. Includes a real incident where one worker held most data, hit full disk, then recovered after scaling that worker to 2 TB.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:13Root cause analysis, alerts, & more
- 2:18Granularity, constant monitoring, filtering, etc
- 4:31System resource metrics
- 7:52Database metrics
- 10:12Citus-specific metrics
related talks
24mCitus from the Customer eyes
32mAuto scaling Azure Cosmos DB for PostgreSQL with Citus, Grafana & Azure Serverless
16mOnline Scale-Out and Cloud Data Ingestion
44mDistributed Postgres with Citus
08mFoundations of Distributed PostgreSQL with Citus
25mSelf Hosted Citus using Cloud Computing
31mKEYNOTE: The Distributed PostgreSQL Problem & How Citus Solves it
32mWhat I learned benchmarking Citus & Postgres performance with HammerDB
