Skip to content

Conversation

@pichlermarc
Copy link
Member

@pichlermarc pichlermarc commented Dec 4, 2025

Fixes #2928

Changes

Adds messaging_latest_experimental as a possible value to SEMCONV_STABILITY_OPT_IN for instrumentations that want to update to the latest semconv without breaking end-users while messaging semconv is still in-development.

The updated spec is also written in a way that once the messaging spec becomes stable, there's an opt-in flag for enabling the latest in-development semconv (attributes for instance) without having it on by default.

Note: I think the name of the flag could be aligned to be messaging/latest-experimental to follow a similar format to messaging/dup, but choose to align with the GenAI semconv for now where genai_latest_experimental is already used.

Merge requirement checklist

  • CONTRIBUTING.md guidelines followed.
  • Change log entry added, according to the guidelines in When to add a changelog entry.
    • If your PR does not need a change log, start the PR title with [chore]
  • Links to the prototypes or existing instrumentations (when adding or changing conventions)

@github-actions github-actions bot added enhancement New feature or request area:messaging labels Dec 4, 2025
@github-project-automation github-project-automation bot moved this to V1 - Stable Semantics in Spec: Messaging Semantics Dec 4, 2025
@pichlermarc pichlermarc force-pushed the feat/pichlermarc/messaging-opt-in branch 2 times, most recently from 1896e09 to 69bbbf4 Compare December 4, 2025 12:13
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version as a comma-separated list of category-specific values
> (e.g., http, databases, messaging). The list of values includes:
> * `messaging` - emit the new, stable messaging conventions,
Copy link
Member

Choose a reason for hiding this comment

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

Should we be crystal clear here and say that this only emits stable conventions? Because it says "stop emitting the old, experimental. I kinda don't like "old" here because there might be "new" unstable conventions as well, and are those included or not? :D

Maybe we just say: emit only stable messaging conventions. and keep it short.

Could also be done as a follow up. I just wanted to bring here now for discussions. CC @open-telemetry/specs-semconv-maintainers

Copy link
Member Author

Choose a reason for hiding this comment

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

I kinda don't like "old" here because there might be "new" unstable conventions as well, and are those included or not? :D

Heh, good point! I'm happy to follow-up on it if we decide to go that route. 🙂

Maybe we just say: emit only stable messaging conventions. and keep it short.

I like that. Maybe that small change could be the resolution for #3200 🙂

@github-actions
Copy link

github-actions bot commented Jan 3, 2026

This PR has been labeled as stale due to lack of activity. It will be automatically closed if there is no further activity over the next 7 days.

@github-actions github-actions bot added the Stale label Jan 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: V1 - Stable Semantics

Development

Successfully merging this pull request may close these issues.

Consider adding messaging_latest_experimental as a possible stabilitly opt-in value

3 participants