How to Use the OpenTelemetry Demo and Why It Matters
summary
Fork of Google’s online boutique becomes a reproducible demo of OpenTelemetry that actually works end to end: 20 microservices instrumented with OpenTelemetry, an OpenTelemetry Collector pipeline, and a default stack (Jaeger traces, Grafana metrics via Prometheus, OpenSearch logs). It supports per-service sampling, Kafka span links, and feature-flagged failure scenarios via flagd/openfeature, and it’s wired to 42 vendors so identical telemetry can be fanned out and compared side-by-side.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:38From online boutique to OpenTelemetry demo
- 7:17Demo goals and value
- 12:42Live demo walkthrough
- 21:33Community feedback and impact
- 21:58Q&A
related talks
35mOpenTelemetry for Busy People
50mGuide to Observability with OpenTelemetry
50mOpen Telemetry: The Rise of Open Standards in Observability
47mA Practical Introduction to Open Telemetry
50mOpen Source Instrumentation - The Rise of OpenTelemetry
02h 02mHow To Troubleshoot and Monitor Applications using OpenTelemetry
38mThe State of OpenTelemetry
34mOpenTelemetry for Dummies: Instrumenting Go Apps