OpenTelemetry standardized the labels. The business meaning still lives outside the trace.
Common names are valuable. They are not the same as common accountability.
OpenTelemetry's semantic conventions do something practical and underrated: they give telemetry data a common naming scheme. That makes the trace readable. It does not make the business event agreed.
OpenTelemetry defines semantic conventions as common names and attributes for operations and data. The project describes them as span names, metric instruments and units, attribute names, types, meanings, and valid values used across traces, metrics, logs, profiles, and resources. This is controlled vocabulary work in production clothing.
The payoff is real. Shared names make telemetry easier to correlate across codebases, libraries, platforms, and teams. A database span, HTTP request, feature flag evaluation, or generative-AI call can carry standard attributes instead of each team inventing its own private dialect. That is how observability stops being a pile of local folklore.
The limit is just as real. Semantic conventions can say how to name an event. They cannot decide whether the event represents an order, a booking, a quote, a renewal, a fraud case, or a customer interaction the business has never reconciled. A trace can show the path of the undefined thing perfectly. It cannot make the thing defined.
Watch the handoff between engineering semantics and business semantics. If the instrumented event is tied to a controlled business term, the trace becomes evidence. If it is tied only to a local code name, the trace becomes beautifully organized ambiguity.
Telemetry conventions make systems speak consistently. Business definitions make the emitted facts worth trusting.
OpenTelemetry semantic conventions define common names and attributes for operations and data so telemetry can use a shared naming scheme.
The semantic conventions cover multiple telemetry signals, including traces, metrics, logs, profiles, and resources.
Technical naming conventions improve correlation and consumption of telemetry, but they do not settle the business definition represented by an emitted event.
No notes yet. The margin is open.
Sign in to add a note. The margin is moderated — we keep it useful, not cruel.
An industry consortium standardized the file format for metric definitions. The meeting where Finance and Sales disagree is still on your calendar.
Owner Missingdbt open-sourced MetricFlow so agents query one definition. Whichever definition wins by default is now the one the robots inherit.
Dashboard TheaterA define-once layer is an admission that the term was never defined.