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)
- Key middleware (ETCD, MINIO, REDIS, JUICE, VIBE, etc.)
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
Was this page helpful?
Thanks—your feedback helps us improve this page.
What got in the way? (optional)