From zero to developer my one year serendipity journey with OpenTelemetry
summary
Contribution starts with an 8–9 month effort creating the OpenTelemetry Certified Associates exam, then moves to a company proof‑of‑concept: deploy collector, instrument PHP and NodeJS SDKs, and wire traces to an open‑source front end. Instrumentation causes measurable performance regressions, visualization lacks parity with the old APM, and limited SRE capacity prevents production rollout. A GitHub issue about auto‑instrumentation closes after ~6–7 months leading to eBPF auto instrumentation adoption.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:23OpenTelemetry overview
- 1:27What is OpenTelemetry
- 2:32Certification exam
- 3:58Proof of concept
- 5:46Testing challenges
- 7:53Visualization hurdles
- 8:55No production deployment
- 10:21Lessons learned
- 11:43Local communities
- 13:09Diversifying contributions
- 13:49OpenTelemetry gateway
- 14:56Call to action
related talks
18mBuilding an APM with OpenTelemetry and OpenSource
23mOpenTelemetry Auto Instrumentation for Effortless Observability
37mHow To Adopt OpenTelemetry in an Enterprise Where Incumbent Vendor Tools Reign Supre...
35mTales of Adopting OpenTelemetry: A First-Timer Journey
47mWhat’s New in OpenTelemetry
33mThe Observant Developer - OpenTelemetry from code to prod
13mWelcome + Opening Remarks
26mObservability for Your Internal Developer Platform: Instrumenting Bac...