From zero to developer: my one year serendipity journey with OpenTelemetry
summary
One-year journey from zero to developer: builds a proof of concept to replace a commercial APM with OpenTelemetry, forks the demo to add a VictoriaMetrics datasource, and spends eight months coauthoring the first OpenTelemetry exam (released 2025). Finds measurable application overhead and long rollout times, pushes issues that spawn an eBPF SIG, starts a Romanian localization SIG, and earns community recognition while planning code contributions.
AI-written summary · about
chapters (14)
- 0:00Introduction and journey
- 2:20Finding motivation to contribute
- 4:11First contribution to OpenTelemetry
- 6:41Challenges in OpenTelemetry adoption
- 9:57Frustration and staying engaged
- 11:00Becoming an individual contributor
- 13:10Localization contributions
- 15:19Starting Romanian OpenTelemetry group
- 16:26Community impact and feedback
- 18:34VictoriaMetrics and OpenTelemetry
- 20:20New OpenTelemetry initiatives
- 22:28Future contributions and advice
- 25:37Importance of user feedback
- 26:21Closing and resources
related talks
16mLightning Talk: From Zero To Developer: My One Year Serendipity Journey With OpenTele...
37mHow To Adopt OpenTelemetry in an Enterprise Where Incumbent Vendor Tools Reign Supre...
13mWelcome + Opening Remarks
15mOpenTelemetry: The Vision, the Reality and How To Get Started
42mOTel Me How To Get My Open Source Community Taken Seriously: Lessons...
34mOpenTelemetry and Epsagon - a Love Story in Three Acts
36mObservability For You and Me with OpenTelemetry
19mOpenTelemetry's Path to Observability's Future
