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 transforms your traces from simple operation logs into powerful debugging and analysis tools. This guide targets developers who are: Instrumenting their own applications with custom spans and attributes Enriching telemetry beyond what auto-instrum...| Blog on OpenTelemetry
One of the most fundamental yet often overlooked aspects of good instrumentation is naming. This post is the first in a series dedicated to the art and science of naming things in OpenTelemetry. We’ll start with spans, the building blocks of a distributed trace, and give you the most important takeaway right at the beginning: how to name the spans that describe your unique business logic. Naming your business spans While OpenTelemetry’s automatic instrumentation is fantastic for covering ...| Blog on OpenTelemetry
Every day, thousands of people are having conversations on GitHub around code, design, bugs, and new ideas. Sometimes there are complex and nuanced points to be made, but other times…| The GitHub Blog
Help us prioritize work in OpenTelemetry by contributing to GitHub issues with your votes and comments.| OpenTelemetry