Observing the HashiCorp Ecosystem From Prometheus
summary
Shows how to configure Prometheus to scrape Consul and Vault: use consul_sd_config or the official consul_exporter, set scrape intervals to 15–30s, point metrics path to the agent telemetry endpoint, and disable hostname in Consul telemetry to avoid duplicate labels. Monitor Consul leader, raft peer count and autopilot health; monitor Vault up/unsealed and audit log success. Read Vault tokens from files (Vault Agent), and use inhibition rules so only actionable alerts (e.g. Vault sealed) page on-call.
AI-written summary · about
chapters (9)
- 0:00Introduction and speakers
- 2:51Prometheus ecosystem evolution
- 8:50Monitoring vs observability
- 13:21Prometheus data model
- 17:33Alerting philosophy
- 19:21Consul telemetry setup
- 23:15Vault monitoring essentials
- 26:07Alert inhibition in practice
- 27:49Dashboarding best practices
related talks
24mObservability with HashiCorp Consul Connect (Service Mesh)
47mBuilding Consul at Scale for Brownfield Infrastructure
22mObservability with Consul Connect
20mHashiCorp Vault Operational Intelligence
31mDeep Dive into the Prometheus Operator Ecosystem
22mAdding Observability to HashiCorp Nomad Applications with Grafana
24mFrom Monitoring to Observability: 10 Things to Do with Prometheus in 2020
51mMonitoring and Alerting for Apache Solr with the Prometheus Stack