Interview › Istio & Service Mesh
What observability gaps does Istio NOT fill that you still need application instrumentation for?
Istio & Service Mesh · Advanced level
Answer
Istio does not replace application instrumentation. It shows network-level service telemetry, but it cannot fully explain business transactions, internal code paths, database query causes, cache hit logic, queue processing, or domain-specific correctness without application metrics and traces.
Technical explanation
The proxy sees requests at service boundaries, not every function call inside a process.
It cannot know why an order failed validation or which SQL query caused latency unless the app emits that context.
Use Istio telemetry with OpenTelemetry, structured logs, RED/USE metrics, and business KPIs.
Hands-on example
Example gap:
Istio shows checkout -> payment returns 500.
Application telemetry shows the actual reason: payment provider timeout after fraud-rule lookup.
Database metrics show fraud_rules query p99 increased.
Without app and DB instrumentation, the mesh only identifies the failing edge.
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?