The Problem with OpenTelemetry
I regularly complain about OpenTelemetry, so with an aim to be a less useless contributor, today I'm putting pen to paper. If you're an implementer, I ask you to read this and take away the personal bias you might have towards your work, and instead look objectively at the feedback being given.
The Problem with OpenTelemetry Edit: tl;dr tracing should exist in every ecosystem, and be broken out of OpenTelemetry. I regularly complain about OpenTelemetry, so with an aim to be a less useless contributor, today I’m putting pen to paper. If you’re an implementer, I ask you to read this and take away the personal bias you might have towards your work, and instead look objectively at the feedback being given. First, some context, if you’re clueless how you ended up here, I started Sentry. Sentry, for obvious reasons, has a stake in this “instrument your application” race. That said, with ev
Explore this link on the map →saved by
related reading
- Overview | OpenTelemetryopentelemetry.io
- Span Issues when merging async genrators · open-telemetry/opentelemetry-python · Discussion #3792 · GitHubgithub.com
- OpenTelemetry: A Guide to Observability with Go | Blog | Luca Cavallinlucavall.in
- Coding Is No Longer the Constraint: Scaling Developer Experience to Teams and Agents at Spotify | Spotify Engineeringengineering.atspotify.com
- All my favorite tracing tools: eBPF, QEMU, Perfetto, new ones I built and more - Tristan Humethume.ca
- Monitoring is a Painmatduggan.com
- Why is observability so expensive?mattklein123.dev
- Logging, Tracing, Monitoring, et al.alexandruburlacu.github.io
- Go Instrumentation Auto SDK | OpenTelemetryopentelemetry.io
- Tracing: structured logging, but better in every way | Andy Doteandydote.co.uk
- What Full-Stack Observability Requires Todaynewrelic.com
- Peter Bourgon · Go for Industrial Programmingpeter.bourgon.org