Observability in Action for your Service Mesh
summary
Kiali visualizes an Istio service mesh and uses Prometheus metrics and Jaeger traces to pinpoint a latency spike: an app with three portals shows ~70 req/s and flights v1 averages ~91 ms while v2 hits ~202–222 ms and an injected “chaos monkey” adds ~550 ms. Kiali highlights VIP users affected, shows mTLS on all edges, and generates Istio config to suspend v2 (traffic to v2 drops to zero) or shift to a 90/10 split; the demo also uses a replay of the last five minutes.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:49Monolith to Microservices
- 7:36Microservice responsibilities
- 8:53Service Mesh to the rescue
- 48:35Service Mesh architecture
related talks
24mObservability for Istio Service Mesh
05mIgnite: Istio+: Enhancing Observability and Tracing using Kiali and Jaeger
35mIntroduction to service mesh with Istio and Kiali
27mKiali Beyond the Graph – Troubleshooting Istio
13mLightning Talk: Troubleshooting Istio Ambient With Kiali 2.0
01h 01mIstio Service Mesh & pragmatic microservices architecture
56mHow to get a grip on your microservices system using a service-mesh
36mWhat's going on in my cluster?