Distributed Microservices Metrics and Tracing with Istio and OpenCensus
summary
Live demo wires Istio sidecar proxy with OpenCensus auto-instrumentation so network-level traces from Istio and in-process spans from OpenCensus appear in Jaeger together. A simple Node/Go service adds a recursive Fibonacci and sleep; traces grow from ~7–8 spans to ~22 spans and a Prometheus-exposed custom fib counter increments with 100% sampling for the demo. Code runs end-to-end, Node client libraries are still alpha and Prometheus exporter setup is rough but functional.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 1:02Why distributed tracing matters
- 7:51Business metrics vs infrastructure stats
- 10:00OpenCensus and Istio overview
- 13:13Demo setup and network tracing
- 19:10Adding OpenCensus for code-level tracing
- 27:08Custom metrics with OpenCensus
- 35:22Summary and Q&A
related talks
34mIstio 101: Open Source Service Mesh for Microservices
35mPractical and Useful Latency Analysis using Istio and OpenCensus - Varun Talwar
45mTracing Cloud-Native Applications: From stacktrace to Opentracing using Istio
59mDistributed Tracing and Monitoring with OpenCensus
05mIgnite: Istio+: Enhancing Observability and Tracing using Kiali and Jaeger
24mObservability for Istio Service Mesh
20mAchieving Observability into Your Application with OpenCensus
52mEmpower Your Microservices with Istio Service Mesh
