ETCD

This page separates raw metrics from scrape endpoints from recorded metrics computed by vmalert. As of 2026-10-13, files/victoria/rules/etcd.yml defines 9 recording rules. The table lists each name and expression. Recorded metrics come from rule …

Dashboards The ETCD module provides one monitoring dashboard: Etcd Overview. ETCD Overview Dashboard ETCD Overview: Overview of ETCD cluster The dashboard shows key ETCD status information. The ETCD Aliveness panel shows the overall cluster service …

The ETCD module provides two core playbooks. Use etcd.yml to install and configure etcd clusters. Use etcd-rm.yml to remove clusters or members. Architecture Change: Pigsty v3.6+ Since Pigsty v3.6, the etcd.yml playbook focuses on cluster …

Use these standard procedures to administer etcd: 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 …

Before deployment, define the etcd cluster in the configuration inventory. Typical choices are: 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 …

ETCD is a distributed, reliable key-value store for critical system configuration data. Pigsty uses etcd as a DCS (Distributed Config Store). It is critical for PostgreSQL high availability and automatic failover. The ETCD module depends on NODE. The …

The ETCD module organizes production ETCD into clusters. A cluster is a logical entity whose ETCD instances coordinate through the Raft consensus protocol. Each cluster is an autonomous distributed key-value store with at least one ETCD instance. It …