Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain why custom attributes are not recommended to be placed in Otel namespaces #3507

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions specification/common/attribute-naming.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,6 +133,13 @@ To do that consider a few options:
`myuniquemapapp.longitude` is likely fine). Make sure the application name
does not clash with an existing semantic convention namespace.

- It is not recommended to use existing OpenTelemetry semantic convention namespace
as a prefix for a new company- or application-specific attribute name. Doing so
may result in a name clash in the future, if OpenTelemetry decides to use that
same name for a different purpose or if some other third party instrumentation
decides to use that exact same attribute name and you combine that instrumentation
with your own.

- The name may be generally applicable to applications in the industry. In that
case consider submitting a proposal to this specification to add a new name to
the semantic conventions, and if necessary also to add a new namespace.
Expand Down