Using OpenTelemetry in a polyglot environment
summary
Instrumenting the Google Microservices demo (Go, Java, NodeJS, .Net, Python) to produce a single distributed trace, this work shows concrete steps: swap OpenCensus for OpenTelemetry, export OTLP over gRPC with proper SSL creds, add auto instrumentation plus targeted manual attributes and events, use the Java agent and Node tracing.js plugins, deploy with scaffold to Kubernetes on AWS, and get end-to-end traces in Honeycomb.io while also proving baggage propagation and documenting several language-specific pitfalls.
AI-written summary · about
chapters (12)
- 0:00OpenTelemetry intro in polyglot
- 2:29Polyglot needs OpenTelemetry
- 5:15Converting OpenCensus to OTel
- 9:05Go frontend instrumentation
- 14:23Java JVM agent setup
- 17:14Node.js auto tracing
- 20:27Dotnet Core instrumentation
- 22:39Python manual tracing
- 24:48Debug tracing propagation
- 26:34Lessons and language nuances
- 28:20Complex environment examples
- 30:28Future steps and demo
related talks
01h 28mUnderstanding Distributed Systems with OpenTelemetry
38mPractical introduction to OpenTelemetry tracing
51mPractical introduction to OpenTelemetry tracing
55mCloud-Native Observability with OpenTelemetry
34mOpenTelemetry for Dummies: Instrumenting Go Apps
40mPractical introduction to OpenTelemetry tracing
42mObservable Applications Using OpenTelemetry
30mPractical introduction to OpenTelemetry Tracing