[chore] allow category-specific values in OTEL_SEMCONV_STABILITY_OPT_IN#2158
Merged
lmolkova merged 2 commits intoopen-telemetry:mainfrom Apr 22, 2025
Conversation
trask
approved these changes
Apr 22, 2025
lmolkova
approved these changes
Apr 22, 2025
Merged
via the queue into
open-telemetry:main
with commit Apr 22, 2025
5e932ef
14 of 15 checks passed
lmolkova
pushed a commit
to lmolkova/semantic-conventions
that referenced
this pull request
May 13, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR partially addresses open-telemetry/opentelemetry-go-contrib#7246 by introducing support for category-specific values in the OTEL_SEMCONV_STABILITY_OPT_IN environment variable. For example, multiple categories should be supported without error:
Changes
Please provide a brief description of the changes here.
Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.
Merge requirement checklist
[chore]