pgtelemetry

pgtelemetry : SQL monitoring views for database activity, WAL, replication, and storage

Overview

Packages

Source

pig build pkg pgtelemetry;		# build rpm/deb

Install

Make sure PGDG and PIGSTY repo available:

pig repo add pgsql -u   # add both repo and update cache

Install this extension with pig:

pig install pgtelemetry;		# install via package name, for the active PG version

pig install pgtelemetry -v 18;   # install for PG 18
pig install pgtelemetry -v 17;   # install for PG 17
pig install pgtelemetry -v 16;   # install for PG 16
pig install pgtelemetry -v 15;   # install for PG 15
pig install pgtelemetry -v 14;   # install for PG 14

Create this extension with:

CREATE EXTENSION pgtelemetry CASCADE; -- requires pg_stat_statements, plpgsql

Usage

Sources:

• Upstream README
• Extension control file
• Version 1.7 SQL
• Generated object documentation

pgtelemetry version 1.7 is a pure-SQL monitoring bundle. Views and functions summarize relation/database/tablespace size, connections and waits, locks, table access and autovacuum, pg_stat_statements timing and buffers, WAL rate, replication slots, and standby lag.

Example

Preload and install pg_stat_statements first, then install this extension in its fixed pgtelemetry schema:

CREATE EXTENSION pg_stat_statements;
CREATE EXTENSION pgtelemetry;
SELECT * FROM pgtelemetry.database_size;
SELECT * FROM pgtelemetry.connections_by_state;
SELECT * FROM pgtelemetry.longest_running_active_queries LIMIT 10;

Installation is superuser-only. Several objects expose cluster-wide query text, client addresses, sizes, locks, replication state, and other operational metadata; wal_telemetry() also maintains a history table. Grant only the specific views/functions a monitoring role needs, protect exported metrics, set retention for WAL samples, and account for polling cost and PostgreSQL-version changes in statistics catalogs.