Understanding Service Mesh Metric Merging
summary
Explains how Istio exposes a single scrape endpoint that returns metrics merged from the application, Envoy sidecar and Istio agent so Prometheus gets a unified document rather than three scrapes. Uses Prometheus with Kubernetes service discovery and pod annotations (prometheus.io port 8080 path /), injection rewrites those annotations to port 15020 and path /* while storing originals so the agent can fetch app metrics, then scrapes Envoy and adds its own metrics. Notes limitations: no mTLS on that endpoint and it breaks annotation-less setups like Prometheus Operator.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:18Monitoring via metrics
- 3:11Service Mesh
- 4:00Metrics in Istio
- 4:56Metrics merging
- 7:28Considerations
- 8:38Alternative Solutions
related talks
24mObservability for Istio Service Mesh
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
49mMaking Microservices Micro with Istio Service Mesh
36mFine Grained Mesh Metrics for Better Visibility With Native Performance
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
34mService Mesh for Developers
33mPlatform Engineering meets Service Mesh: an SRE love story
24mObservability with HashiCorp Consul Connect (Service Mesh)
