Skip to main content

OpenTelemetry Changelog

This site tracks pull requests to the OpenTelemetry Specification, Semantic Conventions, and Proto Definitions. The following items are tracked:

  • Non-trivial specification changes and releases.
  • New semantic convention areas or stability changes, as well as releases.
  • Updates and releases of the protos.

The goal of this site is to give maintainers a single reference for important cross-functional changes.


To add a Pull Request to this feed, label it with changelog.opentelemetry.io

Unset log record severity is not INFO

Related to https://github.com/open-telemetry/opentelemetry-specification/issues/4478

What

6/21/2025open-telemetry/opentelemetry-specificationclosedBy @pellared

Add specification text for OTEP-0250

Part of #1413 Part of #173 Part of #1060

6/16/2025open-telemetry/opentelemetry-specificationmergedBy @jmacd

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.

6/16/2025open-telemetry/opentelemetry-specificationmergedBy @pellared

Stabilize Event Name parameter of Logger.Enabled

Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4528

What are you trying to achieve?

6/16/2025open-telemetry/opentelemetry-specificationmergedBy @pellared

Release 1.46.0

Metrics

  • Prometheus receiver can expect otel_scope_schema_url and otel_scope_[attribute] labels on all metrics.
6/12/2025open-telemetry/opentelemetry-specificationreleasedBy @carlosalberto

`SeverityNumber=0` MAY be used to represent an unspecified value

Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4478

Changes

6/9/2025open-telemetry/opentelemetry-specificationopenedBy @pellared

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).

6/6/2025open-telemetry/opentelemetry-specificationmergedBy @carlosalberto

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.

6/5/2025open-telemetry/opentelemetry-specificationopenedBy @ArthurSens

prometheus: handle schema URL and scope attributes

Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4223

Prototypes:

6/5/2025open-telemetry/opentelemetry-specificationmergedBy @pellared

Initial semantic conventions for mainframes

Fixes #1687

Changes

6/4/2025open-telemetry/semantic-conventionsmergedBy @rrschulze
Page 1 of 7
RSS FeedGitHub

Built with Next.js and Tailwind CSS