Istio integration

The Istio integration provides service mesh monitoring for Kubernetes environments running Istio.


What it’s for	Monitoring service-to-service traffic, latency, and mesh health
Who uses it	Platform engineers, SREs managing Kubernetes with service mesh
Under the hood	Collects metrics from Istio control plane and Envoy sidecars

Metrics collected

The integration collects mesh traffic and Envoy proxy metrics:

Traffic: Request volume by service pair
Latency: P50, P90, P99 by service
Errors: HTTP status codes, failures
Envoy: Sidecar proxy metrics

What to know

This is advanced monitoring, best added after your core Kubernetes observability is in place.

Prebuilt dashboards: mesh overview, services
Prebuilt alerts: error rates, latency
Service-to-service visibility
Pairs with distributed tracing: drill from a latency spike into traces to find the slow service

Documentation

View the full documentation. We’ll add an interactive learning path here when one is ready for this integration.

Istio integration

Istio is a service mesh for Kubernetes, sitting between your services to handle routing, security, and observability. The integration gives you visibility into that mesh layer.

Traffic metrics show which services talk to each other, latency metrics surface how long service-to-service calls take, and error rates highlight failing interactions. It also exposes metrics from Envoy, the sidecar proxy Istio runs alongside each service that actually handles the traffic.

Watch cardinality in large meshes, since metrics are labeled by both source and destination service. The integration pairs well with distributed tracing: when mesh metrics show a latency spike, you can drill into traces to find the slow service.

This is advanced monitoring, best after your core Kubernetes observability is in place.

Istio integration