Observability with Consul Connect
summary
Sets up Consul Connect sidecars (via consul connect proxy) to terminate mTLS with Envoy and expose an Envoy prometheus endpoint bound to a local port so Prometheus scrapes metrics through Consul service discovery. Logs flow to Loki either by Envoy writing files and promtail or via the Docker plugin (beware blocking on plugin failures). Traces export to Tempo from Envoy (Zipkin/OpenTelemetry) and Grafana links logs to traces by trace_id, proving full metrics+logs+traces observability for the mesh.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:33Load Balancers
- 2:22Service Discovery
- 2:58Set Up a Service in Console
- 4:42Service Meshes
- 5:15How Do I Extend My Service Definition for a Service To Become Console Connected
- 7:50Acls
- 11:27How Do I Expose My Prometheus Metrics
- 13:02How To Collect this in Prometheus
- 13:26Consoles Service Discovery
- 15:04How Do We Connect Gravana to Our Prometheus
- 15:51Logs
related talks
24mObservability with HashiCorp Consul Connect (Service Mesh)
39mNetwork Observability with Envoy
22mAdding Observability to HashiCorp Nomad Applications with Grafana
25mThe Lean Observability Stack: Quick and Native Telemetry for Service...
28mObserving the HashiCorp Ecosystem From Prometheus
39mObservable Elixir
27mObservability with Prometheus and beyond
29mParanoid Observability –Success Stories and Misfortunes observing an observability stack