If applications discover each other through Consul, operators need to know whether registered services and their health checks are healthy. Consul Exporter reads selected catalog and health information from Consul and presents it as Prometheus metrics. It helps connect service-discovery observations with the rest of the monitoring system. These checks do not cover every aspect of Consul server performance, and the exporter’s account must have enough permission to see the intended services without exposing unrelated directory or key-value information.
Current guidance
Its current metric list includes service/node health, raft peer counts and optional selected key/value entries. These observations differ from a complete profile of Consul server performance, so decide whether native Consul telemetry is also needed.
Configure the correct Consul address, datacenter, TLS trust and ACL token for the target environment. Service IDs, node names and tags can become Prometheus labels; consider both cardinality and whether infrastructure metadata should be visible to every metrics consumer. Do not enable key/value export without reviewing exactly which values may leave Consul.
During chart replacement, preserve scrape labels used by alerts and verify that a failed Consul query changes the exporter’s health metric as expected. Compare service-health results against a deliberately unhealthy test service, and check behavior during leader or endpoint changes. A running exporter is not proof that it can see every intended service through its ACL policy. No Consul availability or failover test was performed for this record.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Export Consul service health to Prometheus.
Exported Metrics
| Metric | Meaning | Labels |
|---|---|---|
| consul_up | Was the last query of Consul successful | |
| consul_raft_peers | How many peers (servers) are in the Raft cluster | |
| consul_serf_lan_members | How many members are in the cluster | |
| consul_catalog_services | How many services are in the cluster | |
| consul_catalog_service_node_healthy | Is this service healthy on this node | service, node |
| consul_health_node_status | Status of health checks associated with a node | check, node, status |
| consul_health_service_status | Status of health checks associated with a service | check, node, service, status |
| consul_catalog_kv | The values for selected keys in Consul’s key/value catalog. Keys with non-numeric values are omitted | key |
Sources & further reading
Spotted something that needs another look?
Help improve this page →