Otel Semantic Conventions

Handles OpenTelemetry attribute selection and placement so you don't end up with custom attributes that should have been in the registry or metric attributes that explode cardinality. Walks you through the attribute registry lookup, stability checks, and the resource versus span placement decision. The examples are practical: shows you why http.request.method beats custom.http.verb, why service.name belongs on resources not spans, and why user IDs will wreck your metrics if you're not careful. Built by dash0, so it includes their derived attributes and feature dependencies alongside the standard conventions. Good for code reviews and migration work when you're moving between semconv versions.