etcd OpenTelemetry Assets

etcd is a distributed, reliable key-value store used as the backing store for service discovery, configuration management, and coordination in distributed systems. It is the primary data store for Kubernetes, where every cluster state change flows through etcd.

This content pack provides dashboards, alert rules, and SLO templates for monitoring etcd using OpenTelemetry. The assets consume metrics from the Prometheus receiver scraping etcd's /metrics endpoint and cover Raft consensus health, storage saturation, gRPC traffic, and resource usage.

The etcd OpenTelemetry assets have been tested with:

• OpenTelemetry Collector Prometheus receiver with EDOT Collector v9.2.1
• OpenTelemetry Collector Prometheus receiver with OpenTelemetry Collector Contrib v0.146.1

etcd tested against:

• etcd 3.5.x

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

etcd exposes a Prometheus-format metrics endpoint at /metrics by default. Ensure the OTel Collector can reach this endpoint on each etcd member. In Kubernetes, the metrics are typically exposed on port 2381 or using a dedicated metrics port. No additional etcd configuration is required.

Configure the OpenTelemetry Collector (or Elastic Agent with the OpenTelemetry integration) to scrape etcd metrics and export them to Elasticsearch. The following example uses the Prometheus receiver and the elasticsearch/otel exporter with mapping.mode: otel.

receivers:
  prometheus:
    config:
      scrape_configs:
        - job_name: etcd
          scrape_interval: 10s
          scrape_timeout: 10s
          metrics_path: /metrics
          static_configs:
            - targets: [<ETCD_TARGETS>]

processors:
  resource/dataset:
    attributes:
      - key: data_stream.dataset
        value: etcd.otel
        action: upsert
  batch:
    timeout: 10s
    send_batch_size: 1024

exporters:
  elasticsearch/otel:
    endpoints: [${env:ELASTICSEARCH_ENDPOINT}]
    user: ${env:ELASTICSEARCH_USER}
    password: ${env:ELASTICSEARCH_PASSWORD}
    mapping:
      mode: otel
    metrics_dynamic_index:
      enabled: true

service:
  pipelines:
    metrics:
      receivers: [prometheus]
      processors: [resource/dataset, batch]
      exporters: [elasticsearch/otel]
		

Refer to the Prometheus receiver metadata and etcd metrics documentation for details on the metrics produced when scraping etcd's /metrics endpoint. The assets use metrics such as etcd_server_has_leader, etcd_server_proposals_*, etcd_mvcc_*, grpc_server_handled_total, and process_*.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.

← →

×

×

×

×