Module: ETCD

This snapshot records 177 monitoring metric families for the ETCD module. The metrics present at runtime vary with package version, enabled collectors, and target state. Metric Name Type Labels Description etcd:ins:backend_commit_rt_p99_5m Unknown …

Dashboards ETCD module provides one monitoring dashboard: Etcd Overview. ETCD Overview Dashboard ETCD Overview: Overview of ETCD cluster Dashboard provides key ETCD status info. Notable: ETCD Aliveness—shows overall etcd cluster service status. Red …

The ETCD module provides two core playbooks: etcd.yml for installing and configuring etcd clusters, and etcd-rm.yml for removing etcd clusters or members. Architecture Change: Pigsty v3.6+ Since Pigsty v3.6, the etcd.yml playbook focuses on cluster …

Common etcd admin SOPs: Create Cluster: Initialize an etcd cluster Destroy Cluster: Destroy an etcd cluster CLI Environment: Configure etcd client to access server cluster RBAC Authentication: Use etcd RBAC auth Reload Config: Update etcd server …

Before deployment, define etcd cluster in config inventory. Typical choices: One Node: No HA, suitable for dev, test, demo, or standalone deployments using external S3 backup for PITR Three Nodes: Basic HA, tolerates 1 node failure, suitable for …

ETCD is a distributed, reliable key-value store for critical system config data. Pigsty uses etcd as DCS (Distributed Config Store), critical for PostgreSQL HA and automatic failover. The ETCD module depends on NODE module and is required by PGSQL …

The ETCD module organizes ETCD in production as clusters—logical entities composed of a group of ETCD instances associated through the Raft consensus protocol. Each cluster is an autonomous distributed key-value storage unit consisting of at least …