The OpenTelemetry community has grown tremendously over the past few years, and with that growth comes valuable insights hidden in our community conversations. We analyzed nearly 10,000 messages from the #otel-collector and #opentelemetry Slack chann...
Imagine the perfect observability world: There is an incident, the on-call team gets paged in the middle of the night, wakes up and thanks to your telemetry, the root-cause is identified within just a
TL;DR: We're launching OllyGarden Tulip, a commercially supported OpenTelemetry Collector distribution with stable releases, predictable upgrade paths, and professional support from the people who helped build the Collector. It's open source and free...
Every team discovers OpenTelemetry the same way. First, excitement—finally, visibility into distributed systems! Then comes the instrumentation party. Spans everywhere. Every function. Every validation. Every calculation gets its own span because "mo...
Metrics are the quantitative backbone of observability—the numbers that tell us how our systems are performing. This is the third post in our OpenTelemetry naming series, where we've already explored how to name spans and how to enrich them with mean...
Welcome to the second installment in our series on OpenTelemetry naming best practices. In our previous post, we explored how to name spans using the {verb} {object} pattern. Today, we're diving into span attributes, the rich contextual data that tra...
