Add specification text for OTEP-0250
Stabilize SDK and No-Op Logger.Enabled
This part of the specification can be stabilized.
It primarily defines how the SDK should respond to Logger.Enabled
calls.
I believe adding new rules in this context should not be considered breaking changes.
Stabilize Event Name parameter of Logger.Enabled
Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4528
What are you trying to achieve?
Release 1.46.0
Metrics
- Prometheus receiver can expect
otel_scope_schema_url
andotel_scope_[attribute]
labels on all metrics.
`SeverityNumber=0` MAY be used to represent an unspecified value
Have InstrumentationScope use normative language
Fixes #4450
Moved the InstrumentationScope
definition from glossary into common/instrumentation-scope.md, and massaged it using normative language, including some examples. Also removed the compile-time concept restriction (as clarified in the related issue, this limitation does not exist in a few SIGs).
sdk_exporters/prometheus: Clarify Content Negotiation
Changes
Addressing feedback received during the last Spec SIG meeting, I'm splitting my previous PR(https://github.com/open-telemetry/opentelemetry-specification/pull/4533) into two to ensure we keep the scope of the original one for the configuration changes.
prometheus: handle schema URL and scope attributes
Initial semantic conventions for mainframes
Fixes #1687