Skip to content

Monitoring System

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

Pigsty’s monitoring system has three pillars—metrics, logs, and alerting—and is available out of the box. Logs and alerts are also important inputs for audit and traceability. It can monitor clusters managed by Pigsty, 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 monitoring onboarding modes:

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