etcd Plugin

The etcd plugin registers an etcd cluster as one Konduo resource and exposes member, endpoint, alarm, proposal, MVCC DB size, peer, and network signals to the operator UI.

Highlights

• Uses both HTTP gateway and etcd v3 gRPC client paths for member, status, and alarm evidence.
• Connects member discovery, leader/learner state, endpoint health, HashKV, and NOSPACE alarms to diagnostics.
• Supports Prometheus mapping packs and Konduo-managed metric collection.
• Protects recovery-support actions such as compact, defrag, alarm disarm, snapshot, and leader transfer with confirmation and cooldown controls.

Before Registration

• Prepare etcd client endpoints, TLS/mTLS, basic auth, and timeout settings.
• Set metric_collection_endpoints when /metrics is exposed on a separate listener.
• In gRPC-only environments, only a status-derived subset may be collected; review p99 latency and histogram panel coverage.

Operations Tips

• Distinguish client URLs from peer URLs when reading member evidence.
• Treat fallback evidence as partial when gateway discovery fails.
• Confirm revision, target endpoint, and operator intent before running defrag or compact actions.

---

etcd Enterprise Overlay

The etcd Enterprise overlay adds MCP descriptors, anomaly rules, and plugin-executed detectors on top of the Community etcd plugin. Its goal is to surface cluster risk earlier by correlating quorum, leader, proposal, WAL, and fsync signals.

Highlights

• Exposes etcd resources, monitoring overview, diagnostics, metrics mapping, and anomaly rules through the MCP catalog.
• Plugin-executed anomaly detectors interpret etcd API evidence together with metric evidence.
• Declarative metric rules resolve logical metric keys through a Prometheus metric source.
• Simulator fixtures cover leader instability, quorum risk, disk latency, and proposal backlog scenarios.

Before Registration

• Community etcd connectivity and TLS settings must be healthy.
• Anomaly analysis needs a Prometheus metric source and mapping pack linkage.
• MCP users need read scopes and resource access.

Operations Tips

• Interpret leader changes, proposal backlog, and fsync latency together with quorum state instead of as isolated signals.
• When plugin detector and declarative metric results differ, check metric-source coverage and etcd API permissions first.