Skip to content

Document OTEL_SEMCONV_STABILITY_OPT_IN environment variable#4254

Open
thakoreh wants to merge 1 commit intoopen-telemetry:mainfrom
thakoreh:document-semconv-stability-opt-in
Open

Document OTEL_SEMCONV_STABILITY_OPT_IN environment variable#4254
thakoreh wants to merge 1 commit intoopen-telemetry:mainfrom
thakoreh:document-semconv-stability-opt-in

Conversation

@thakoreh
Copy link

Description

Fixes issue #4202 - Document the OTEL_SEMCONV_STABILITY_OPT_IN environment variable.

Changes

Added a new subsection under Semantic Convention status explaining:

  • How to use OTEL_SEMCONV_STABILITY_OPT_IN
  • Available options (http, http/dup)
  • Default behavior (old experimental conventions)
  • Example usage with multiple opt-ins

Documentation Added

  • Explains http vs http/dup modes
  • Shows example environment variable usage
  • Documents default behavior

Add documentation explaining how to use the OTEL_SEMCONV_STABILITY_OPT_IN
environment variable to control semantic convention stability opt-in for
HTTP instrumentations.

Fixes: open-telemetry#4202
@thakoreh thakoreh requested a review from a team as a code owner February 24, 2026 14:16
@xrmx xrmx moved this to Easy to review / merge / close in Python PR digest Feb 24, 2026

### Opting into stable semantic conventions

You can control which semantic conventions are used by setting the `OTEL_SEMCONV_STABILITY_OPT_IN` environment variable. This is useful for transitioning from experimental to stable semantic conventions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is the wrong place, I think we should have these to every http instrumentation rst documentation and maybe on opentelemetry.io

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with xrmx. It will be a bigger update, but the individual docs are a better place for details especially for users doing manual instrumentation. For example: one update in the Flask readthedocs already linked from Flask readme

@xrmx xrmx moved this from Easy to review / merge / close to Reviewed PRs that need fixes in Python PR digest Feb 24, 2026
@thakoreh
Copy link
Author

Thanks for the feedback @xrmx @tammy-baylis-swi! You're right - the documentation belongs in the individual instrumentation READMEs rather than the root README. I'll update this PR to add the env var documentation to the Flask instrumentation README and link it from there.

Let me refactor this to target the specific instrumentation docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Reviewed PRs that need fixes

Development

Successfully merging this pull request may close these issues.

3 participants