Skip to content

Commit d67c878

Browse files
Clarify usage of "otel." attribute namespace
I noticed developers adding their own attributes to this namespace without going through the specification. We need to regulate this namespace through the specification, just like we do it for other semantic conventions.
1 parent d0d2b48 commit d67c878

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

specification/common/attribute-and-label-naming.md

+13
Original file line numberDiff line numberDiff line change
@@ -130,3 +130,16 @@ It is recommended to limit names to printable Basic Latin characters
130130
(more precisely to
131131
[U+0021 .. U+007E](https://en.wikipedia.org/wiki/Basic_Latin_(Unicode_block)#Table_of_characters)
132132
subset of Unicode code points).
133+
134+
## otel.* Namespace
135+
136+
Attribute names that start with `otel.` are reserved to be defined by
137+
OpenTelemetry specification. These are typically used to express OpenTelemetry
138+
concepts in formats that don't have a corresponding concept.
139+
140+
For example `otel.library.name` attribute is used to record the instrumentation
141+
library name, which is an OpenTelemetry concept that is natively represented in
142+
OTLP, but does not have an equivalent in other telemetry formats and protocols.
143+
144+
Any additions to `otel.*` namespace should be approved as part of OpenTelemetry
145+
specification.

0 commit comments

Comments
 (0)