Keynote: Service Meshes and Observability
summary
Service mesh handles discovery, interconnection, load balancing and auth at the RPC boundary, but explaining why a transaction is slow requires distributed tracing stitched end-to-end. OpenTracing acts as a lingua franca that lets Envoy, Linkerd, Conduit and nginx forward trace context to Jaeger, LightStep or other backends. Demo shows donut-zone under audience load, a Lyft case shows Envoy enabling tracing across hundreds of services with one config change, and traces reveal concrete root causes like mutex contention with 20 waiters dominating latency.
AI-written summary · about
chapters (6)
related talks
46mObserving chaos: how distributed tracing brings observability to a service mess
20mKeynote: Prometheus, Jaeger, and Envoy: The Observability for Today's Enterprises
19mKeynote: OpenTracing and Containers: Depth, Breadth, and the Future of Tracing - Ben Sigelman
31mUnderstanding Microservices with Distributed Tracing
05mIgnite: Istio+: Enhancing Observability and Tracing using Kiali and Jaeger
53mDo you need a Service Mesh?
07mGetting the most out of service mesh
09mLightning Talk: The Hardest Part of Operating a Service Mesh: Envoy Proxy