Tips And Tricks To Successfully Migrate From Jaeger To OpenTelemetry
summary
Stepwise migration from Jaeger to OpenTelemetry is practical: a Java/Go demo app is fully re‑instrumented live, and a lightweight openTelemetry shim lets repositories switch client libraries by swapping imports in minutes. The OpenTelemetry Collector can be inserted between apps and existing Jaeger collectors to accept OTLP ingestion into Jaeger and duplicate/export to Promscale or other backends. Jaeger’s adaptive samplers remain available if the pipeline forwards appropriately, and the span metrics processor successfully generates Prometheus metrics from traces.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:36Pre-requisites
- 5:05Jaeger Architecture
- 5:36OpenTelemetry Architecture
- 7:22Using OpenTelemetry shim
- 8:12Complete re-instrumentation
- 23:25Difference btw Jaeger & Otel collectors
related talks
47mA Practical Introduction to Open Telemetry
35mOpenTelemetry for Busy People
26mJaeger V2: OpenTelemetry at the Core of Modern Distributed Tracing
45mJaeger: Present and Future
37mOpenTelemetry & Distributed Tracing: A Jaeger v2 Deep Dive
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
28mGetting Started with OpenTelemetry
02h 02mHow To Troubleshoot and Monitor Applications using OpenTelemetry