[configuration] Clarify that the boolean value environment variable guidance is not applicable to other configuration interfaces by mx-psi · Pull Request #4723 · open-telemetry/opentelemetry-specification (original) (raw)

…uidance is not applicable to other configuration interfaces

mx-psi marked this pull request as ready for review

November 5, 2025 13:09

github-merge-queue Bot pushed a commit to open-telemetry/opentelemetry-collector that referenced this pull request

Nov 7, 2025

arminru added a commit to carlosalberto/opentelemetry-specification that referenced this pull request

Dec 10, 2025

Moved clarification about boolean environment variables open-telemetry#4723 to the SDK Configuration section.

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

Dec 12, 2025

Context

• Make the W3C randomness flag required.

(#4761)

Traces

• Deprecate Zipkin exporter document and make exporter implementation optional.

(#4715)

• Add spec for AlwaysRecord sampler

(#4699)

Metrics

• Stabilize Enabled API for synchronous instruments.

(#4746)

• Allow instrument Enabled implementation to have additional optimizations and features.

(#4747)

Logs

• Stabilize LogRecordProcessor.Enabled.

(#4717)

SDK Configuration

• Clarifies that guidance related to boolean environment variables is not applicable to other configuration interfaces. (#4723)

Co-authored-by: Armin Ruech 7052238+arminru@users.noreply.github.com

trask mentioned this pull request

Jan 7, 2026

This was referenced

May 5, 2026

pull Bot pushed a commit to CodeWeaver13/opentelemetry-specification that referenced this pull request

May 11, 2026

Here, I change:

• without_scope_info -> scope_info_enabled (default true)
• without_target_info -> target_info_enabled (default true)
• with_resource_constant_labels -> resource_constant_labels (default none are added)

The with prefix of a few (but not all) prometheus exporter options seems to be a carry over from go functional options pattern. We don't see it in the spec'd property names of any other built in components. It doesn't doesn't contribute to the property's meaning in any way. Omitting it doesn't block a language from using it in their implementation, since that choice falls within maintainer discretion.

I think the use of "without" without_scope_info / without_target_info with a default value of false was probably inspired by the "All Boolean environment variables SHOULD be named and defined such that false is the expected safe default behavior." language that we decided is not applicable to other configuration interfaces: open-telemetry#4723

So since there's no env vars for without_scope_info / without_target_info, we don't need to be constrained by that.

Originated from: open-telemetry#5056 (comment)

Corresponding change in declarative config schema: github.com/open-telemetry/opentelemetry-configuration/pull/612

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