Instrumenting Go Apps With OpenTelemetry
summary
Claims OpenTelemetry lets teams instrument once and export anywhere so you stop rewriting vendor SDKs; demo uses the OTel SDK, an exporter to a collector, a batcher and parent‑based sampling, plus the otelhttp middleware for automatic span creation. Go support has traces and metrics stable, logs beta and auto‑instrumentation alpha. Example shows SQS → chatbot → DB traces merged in one flamegraph, works against DataDog, NewRelic or Grafana/Tempo. Adoption for a Go service is roughly a week.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:01Observability basics
- 3:02The problem with vendor lock
- 4:23Introduction to open telemetry
- 6:08Collector and processors
- 7:34Open telemetry in Go
- 8:08Instrumentation implementation
- 12:26Middleware and client spans
- 13:45Data visualization
- 14:47Open telemetry with grafana
- 15:23Summary and Q&A
related talks
34mOpenTelemetry for Dummies: Instrumenting Go Apps
40mInstrumenting GO Applications
30mMastering Distributed Tracing with Go
01h 28mUnderstanding Distributed Systems with OpenTelemetry
39mEfficient Debugging and Logging with OpenTelemetry in Go
30mOpenTelemetry 101
42mObservable Applications Using OpenTelemetry
01h 00mObservability made painless: Go, Otel & LGTM stack