OpenTelemetry Changelog

Traces

• Define sampling threshold field in OpenTelemetry TraceState; define the behavior

Related to #4468, #4414

This OTEP suggests a path forward on how to support complex attributes. It proposes to:

🚩 Deprecations 🚩

• os: Adds the 'deprecated:' tag/attribute to the z_os enum value of os.type. This value was recently deprecated in v1.35.0. ([#2479](https://github.com/open-telemetry/semantic-conventions/issues/2479))

Changes

This change brings the specification lifecycle phases in alignment with OTEP-232 which defines the maturity levels for OTel in general. Most of the changes should be non-contentious, but one aspect deserves discussion: should feature-freeze be mapped to Release Candidate?

🛑 Breaking changes 🛑

• azure: Align azure events, attributes, and enum members with general naming guidelines. ([#608](https://github.com/open-telemetry/semantic-conventions/issues/608), [#1708](https://github.com/open-telemetry/semantic-conventions/issues/1708), [#1698](https://github.com/open-telemetry/semantic-conventions/issues/1698))

What's Changed

• [ja] docs(i18n): fix drift of content/ja/docs/what-is-opentelemetry.md by @Msksgm in https://github.com/open-telemetry/opentelemetry.io/pull/7017
• [ja] docs(i18n): fix drift of content/ja/docs/languages/_index.md by @Msksgm in https://github.com/open-telemetry/opentelemetry.io/pull/7018

Related to https://github.com/open-telemetry/semantic-conventions/issues/1536

Changes

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

Changes

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.

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

What