Observability with HashiCorp Consul Connect (Service Mesh)
summary
Explains how to instrument a Consul Connect service mesh by enabling Consul Connect sidecar telemetry, exposing Envoy metrics on a local scrape port, and pushing that to Prometheus via Consul service discovery or static targets. Shows central service config and per-service connect stanza snippets, uses Envoy flags to emit proxy logs into files picked up by promtail into Loki, and exports Zipkin-format spans to Tempo, with Grafana dashboards and datasource JSON linking logs and traces by trace ID.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:09Evolution of scaling
- 2:23Service mesh and Consul
- 9:08The pillars of observability
- 10:50Metrics with Prometheus
- 15:18Dashboarding with Grafana
- 16:19Log management with Loki
- 19:55Distributed tracing with Tempo
- 23:11Conclusion
related talks
22mObservability with Consul Connect
28mObserving the HashiCorp Ecosystem From Prometheus
09mLightning Talk: The Hardest Part of Operating a Service Mesh: Envoy Proxy
10mUnderstanding Service Mesh Metric Merging
29mThe Meshery Adapter for HashiCorp Consul
39mNetwork Observability with Envoy
20mService Mesh: A Hole in the Pocket?
29mObservability and Debugging Cloud-Native Apps using Linkerd & Conduit