Interview › Istio & Service Mesh
How does Istio integrate with Prometheus for metrics?
Istio & Service Mesh · Intermediate level
Answer
Istio integrates with Prometheus by exposing proxy and control-plane metrics that Prometheus can scrape. The data plane emits request metrics such as istio_requests_total and duration histograms, while Istio components expose health and operational metrics.
Technical explanation
In production, Prometheus scraping is usually managed by Prometheus Operator ServiceMonitor or PodMonitor resources, or equivalent platform configuration.
Metric cardinality must be controlled; excessive labels can overload Prometheus.
Dashboards and alerts should distinguish workload traffic metrics from mesh control-plane and gateway metrics.
Hands-on example
Prometheus query examples:
Error rate:
sum(rate(istio_requests_total{response_code=~'5..'}[5m])) by (destination_workload)
/
sum(rate(istio_requests_total[5m])) by (destination_workload)
Control plane scrape check:
$ kubectl -n istio-system get svc istiod -o yaml | grep prometheus -A5
Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.
More Istio & Service Mesh interview questions
- What is Istio, and what are the core capabilities it provides?
- What is the difference between the Istio control plane and data plane?
- What is istiod, and what does it do?
- What is Envoy, and what role does it play in Istio?
- What is the sidecar pattern, and how does Istio inject the proxy?
- How does automatic sidecar injection work (namespace label, webhook)?
- What is the Istio ambient (sidecarless) mode, and how does it differ from sidecar mode?
- What is the difference between ztunnel and a waypoint proxy in ambient mode?