Use consistent vocabulary in reference to components and plugins by jack-berg · Pull Request #4806 · open-telemetry/opentelemetry-specification (original) (raw)

Merged via the queue into open-telemetry:main with commit 55d0572

Jan 9, 2026

8 checks passed

jack-berg deleted the consistent-component-vocabulary branch

January 9, 2026 21:07

github-merge-queue Bot pushed a commit that referenced this pull request

Feb 13, 2026

Context

• Deprecate Jaeger propagator and make propagator implementation optional.

(#4827)

• Deprecate OT Trace propagator and make propagator implementation optional.

(#4851)

Metrics

• Add normative language to the Metrics API/SDK spec concurrency requirements.

(#4868)

Logs

• Add optional Exception parameter to Emit LogRecord.

(#4824)

• Add normative language to the Logging API/SDK spec concurrency requirements.

(#4885)

Resource

• Refine the handling of OTEL_RESOURCE_ATTRIBUTES.

(#4856)

Common

• Add string representation guidance for complex attribute value types (byte arrays, empty values, arrays, and maps) for non-OTLP protocols.

(#4848)

Compatibility

• Stabilize Prometheus Counter to OTLP Sum transformation.

(#4862)

• Stabilize Prometheus Gauge to OTLP Gauge transformation.

(#4871)

SDK Configuration

• Swap Tracer/Meter/LoggerConfig disabled for enabled to avoid double negatives

(#4823)

• Declarative configuration: rename ComponentProvider to PluginComponentProvider, CreatePlugin to CreateComponent in effort to use consistent vocabulary

(#4806)

• Declarative configuration: Update instrumentation config behavior to return empty object when not set

(#4817)

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})