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

Clarify that attribute requirement levels apply to instrumentation libraries #3289

Merged
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,10 @@ release.
([#3244](https://github.com/open-telemetry/opentelemetry-specification/pull/3244))
- Mark `net.sock.host.port` as conditionally required.
([#3246](https://github.com/open-telemetry/opentelemetry-specification/pull/3246))
- Clarify that attribute requirement levels apply to instrumentation. And that,
because users can transform their telemetry in a number of ways, these requirement
levels cannot be relied on by telemetry consumers.
([#3289](https://github.com/open-telemetry/opentelemetry-specification/pull/3289))

### Compatibility

Expand Down
4 changes: 4 additions & 0 deletions specification/common/attribute-requirement-level.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,10 @@

_This section applies to Log, Metric, Resource, and Span, and describes requirement levels for attributes defined in semantic conventions._

Attribute requirement levels apply to instrumentation. Because users can transform their telemetry in a number of ways
trask marked this conversation as resolved.
Show resolved Hide resolved
(e.g. metric views, span processors, and collector transformations), these requirement levels cannot be relied on by
telemetry consumers.

The following attribute requirement levels are specified:

- [Required](#required)
Expand Down