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
saved by
related reading
- Span Issues when merging async genrators · open-telemetry opentelemetry-python · Discussion #3792github.com
- OpenTelemetry is a CNCF Graduated Projectopentelemetry.io
- All you need is Wide Events, not “Metrics, Logs and Traces”isburmistrov.substack.com
- Monitoring is a Painmatduggan.com
- OpenTelemetry: A Guide to Observability with Go | Blog | Luca Cavallinlucavall.in
- There's no reason for software to be slow anymoredanluu.com
- Overview | OpenTelemetryopentelemetry.io
- All my favorite tracing tools: eBPF, QEMU, Perfetto, new ones I built and more - Tristan Humethume.ca
- Why is observability so expensive?mattklein123.dev
- GitHub - traceloop/openllmetry: Open-source observability for your GenAI or LLM application, based on OpenTelemetrygithub.com
- Why I Ignore The Spotlight as a Staff Engineer - Lalit Magantilalitm.com
- Logging, Tracing, Monitoring, et al.alexandruburlacu.github.io