Monitoring:etcd monitoring
HertzBeat monitors the etcd key-value store by collecting metrics from the Prometheus metrics endpoint that etcd exposes.
etcd 3.4+ is supported (the database size metric
etcd_mvcc_db_total_size_in_bytesreplaced the oldetcd_debugging_*name in 3.4).
PreRequisites
Make sure HertzBeat can reach etcd's metrics endpoint
etcd exposes Prometheus-format metrics on its client port (default 2379) at the /metrics path. Make sure this address is reachable from HertzBeat:
- If etcd only listens on localhost, or client mutual TLS is enabled on the client port, configure a dedicated metrics listener via
--listen-metrics-urls. It serves the metrics and health-check endpoints; if exposed without TLS, restrict it to a trusted network. - Access
{metrics-host}:{metrics-port}/metrics(the client port2379by default) from the HertzBeat host to confirm metrics data can be fetched.
More information see etcd monitoring documentation.