HashiCorp Consul Integration
Monitor your entire Consul service catalog, health check status, and Raft consensus metrics. Get instant alerts on node failures and service health regressions.
How It Works
Enable Consul Telemetry
Add the telemetry stanza to your consul.hcl configuration. Consul will emit metrics via the StatsD or Prometheus endpoint that TigerOps ingests automatically.
Connect the TigerOps Agent
Point TigerOps at your Consul HTTP API for health check polling and catalog sync. Service registrations and deregistrations appear as annotated events on your dashboards.
Configure Health Check Alerts
Define alert rules for critical service health checks. TigerOps fires immediately when a check transitions to critical and resolves automatically when the service recovers.
Correlate with Service Traffic
When a Consul health check fails, TigerOps automatically correlates the event with traffic metrics from Envoy or Linkerd to show which upstream requests are affected.
What You Get Out of the Box
Service Catalog Monitoring
Track registered services, healthy vs. failing instances, and deregistration events across all datacenters. Get a real-time view of your entire service inventory.
Health Check Tracking
Per-check pass/fail/warning status with state change timestamps, output capture, and alert routing. Never miss a health check failure in a large cluster.
Node Failure Detection
Monitor Consul agent node health, gossip protocol metrics, and Serf member events. Get alerted on node failures and network partitions before they cascade.
Raft Consensus Metrics
Track Raft leader election frequency, commit latency, and follower lag. Raft instability is surfaced as a critical alert before it impacts service discovery.
KV Store Metrics
Monitor KV store operation rates, transaction sizes, and watch trigger counts. Excessive KV watches are surfaced as a performance risk indicator.
Connect Service Mesh
Consul Connect intention metrics, certificate rotation events, and proxy health checks are tracked alongside your Envoy sidecar metrics for full mesh visibility.
consul.hcl Telemetry Configuration
Add the telemetry block to your existing Consul agent configuration.
# consul.hcl — add the telemetry stanza to your existing config
datacenter = "us-east-1"
data_dir = "/opt/consul"
# Enable Prometheus metrics endpoint
telemetry {
prometheus_retention_time = "30s"
disable_hostname = false
# StatsD alternative — point directly to TigerOps
# statsd_address = "statsd.ingest.atatus.net:8125"
# metrics_prefix = "consul"
}
# TigerOps scrape config (prometheus scrape)
# Add this to your tigerops-agent ConfigMap:
#
# scrape_configs:
# - job_name: consul
# metrics_path: /v1/agent/metrics
# params:
# format: [prometheus]
# static_configs:
# - targets:
# - consul.service.consul:8500
# labels:
# datacenter: us-east-1
# cluster: prod
# authorization:
# credentials: "${CONSUL_HTTP_TOKEN}"
#
# remote_write:
# - url: https://ingest.atatus.net/api/v1/write
# bearer_token: "${TIGEROPS_API_KEY}"
# Optional: watch health checks via TigerOps API integration
# Configure in TigerOps dashboard:
# Integration > Consul > HTTP API
# Endpoint: https://consul.example.com:8500
# Token: <read-only ACL token>
# Poll interval: 15s
# Alert on: critical, warningCommon Questions
Which Consul versions does TigerOps support?
TigerOps supports HashiCorp Consul 1.8 and later, including Consul Enterprise. Both OSS and Enterprise telemetry metrics are supported. Consul on HCP (HashiCorp Cloud Platform) is also supported via the HTTP metrics endpoint.
Can TigerOps monitor Consul across multiple datacenters?
Yes. Deploy a TigerOps scraper in each datacenter and tag metrics with a datacenter label. The TigerOps workspace aggregates metrics across all datacenters for unified visibility and cross-datacenter alert correlation.
How does TigerOps handle Consul health check flapping?
TigerOps includes a configurable flap suppression window. If a health check transitions between passing and critical within a short window, TigerOps fires a single "flapping" alert instead of spamming your on-call channel.
Can I use TigerOps to alert on Consul ACL token expiry?
Yes. The TigerOps Consul integration monitors ACL token TTLs via the Consul API and fires a warning alert a configurable number of days before expiration. This prevents unexpected authentication failures.
Does TigerOps support Consul Service Mesh (Connect) telemetry?
Yes. When Consul Connect is enabled, TigerOps ingests proxy sidecar metrics including TLS handshake rates, connection pool stats, and intention enforcement counts alongside standard Consul metrics.
Never Miss a Consul Health Check Failure Again
Service catalog monitoring, Raft health, and instant health check alerts. Connect in minutes.