Monitoring System

How Pigsty’s monitoring system is architected and how monitored targets are automatically managed.

The built-in monitoring system provides metrics, logs, and alerting. Logs and alerts also support audit and traceability. It can monitor Pigsty-managed clusters, existing PostgreSQL clusters, and external RDS services.

Monitoring Targets

Pigsty monitoring covers these core targets:

PostgreSQL clusters and instances (SQL performance, connections, replication, transactions, checkpoints, WAL)
Infrastructure components (Grafana, VictoriaMetrics, Alertmanager, Nginx, etc.)
Host nodes (CPU, memory, disk, network, kernel)
Other service modules (ETCD, MINIO/Silo, REDIS/Valkey, KAFKA, MYSQL, JUICE, VIBE, etc.)

Monitoring Scale and Counting Method

Pigsty v4.5.0’s dashboard directory and Victoria rule directory contain:

Source Group	Dashboards	Recording Rules	Alert Rules
PGSQL	29	402	16
NODE	10	163	16
INFRA	11	2	2
ETCD	0	9	5
REDIS	3	96	6
MINIO / Silo	2	0	5
KAFKA	4	19	15
MYSQL	5	68	27
APP	2	0	0
Pigsty Overview	1	0	0
Agent Liveness	0	14	0
Total	67	773	92

Dashboards are counted as files/grafana/**/*.json files; ETCD dashboards reside in the INFRA directory. Recording and alert rules count record and alert entries in files/victoria/rules/*.yml, plus 14 liveness recording rules generated by the agent.yml template: 759 + 14 = 773. These are configuration counts shipped in the source. Deployed modules and settings determine what is actually loaded.

Raw exporter metrics and time-series counts vary with component versions, collectors, and monitored objects. Use the running scrape endpoints as the authority.

Technology Stack

Component	Purpose
Grafana	Visualization dashboards, unified entry point, alert views
VictoriaMetrics	Time-series metric ingestion, storage, and query
VictoriaLogs	Structured log ingestion, indexing, and search
VMAlert + Alertmanager	Alert rule evaluation and notification delivery
Exporter / Agent	Database/system metric exposure and log forwarding

Onboarding Modes

Pigsty supports three ways to add monitoring:

Mode	Use Case	Entry
`FULL`	Database is deployed and managed directly by Pigsty	PGSQL Monitoring System
`MANAGED`	Existing PostgreSQL cluster with SSH-manageable nodes	Monitor Existing Cluster
`RDS`	Cloud database accessible only by connection string	Monitor RDS

Continue Reading

PGSQL Monitoring System: Database metrics, logs, alerting, and dashboards
INFRA Monitoring & Alerting: Health of the monitoring stack itself
NODE Monitoring & Alerting: Host resource and system health
ETCD Monitoring & Alerting: Consistency and availability monitoring
MINIO Monitoring & Alerting: Object storage cluster monitoring
REDIS Monitoring & Alerting: Cache cluster runtime monitoring
KAFKA Monitoring & Alerting: Brokers, topics, consumers, and optional JMX metrics
MYSQL Monitoring & Alerting: Instances, clusters, and replication state