A Prometheus exporter that collects and exposes Consul service health, cluster state, and key/value metrics for monitoring.
Consul Exporter is a Prometheus exporter that collects metrics from HashiCorp Consul instances. It exposes Consul's service health status, cluster membership information, and key/value store data as Prometheus metrics, enabling operators to monitor the state and performance of their Consul service mesh and service discovery infrastructure.
DevOps engineers, SREs, and platform teams who use Consul for service discovery and service mesh and need to monitor its health and performance using Prometheus.
It provides a standardized, reliable way to integrate Consul's operational data into Prometheus monitoring stacks without custom scripting, offering detailed insights into service health and cluster state.
Exporter for Consul metrics
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Exports metrics like `consul_catalog_service_node_healthy` to precisely track service health per node, enabling alerting on failures as shown in the README's useful queries.
Provides metrics on Raft peers and Serf members (e.g., `consul_raft_peers`, `consul_serf_lan_member_status`) for monitoring cluster health and cross-datacenter WAN status.
Supports exposing numeric values from Consul's KV store as metrics using prefixes and regex filters, useful for tracking configuration changes without custom code.
Offers numerous flags for TLS, authentication, request limits, and Docker deployment, allowing customization for various security and scalability needs.
Enabling `consul.health-summary` requires n+1 API queries to Consul, which can strain servers in large clusters, as the README warns this is enabled by default.
Only numeric values from the KV store are exposed; non-numeric values are omitted, restricting use for monitoring all configuration data, as admitted in the metrics table.
As a pure exporter, it provides raw metrics without dashboards, necessitating additional setup with tools like Grafana, which adds complexity to the monitoring stack.
Configuring TLS, authentication, and KV filters requires careful handling of flags and files, which can be error-prone for less experienced users.