-
Notifications
You must be signed in to change notification settings - Fork 278
Description
Area(s)
area:messaging
What's missing?
In the OTel JS Contrib repo, we have a bunch of instrumentations that are using very outdated versions of semantic conventions. Every once in a while, motivated contributors come around that are interested in updating these instrumentation to the latest experimental semantic conventions (example: open-telemetry/opentelemetry-js-contrib#2976).
Unfortunately, we don't have a "safe" way forward for such changes at the moment as the messaging semconv only specifies messaging and messaging/dup as possible values to be used once the messaging semantic conventions become stable.
Describe the solution you'd like
In the Gen AI Semantic Conventions' section about stability opt-in there's a gen_ai_latest_experimental value that can be set in OTEL_SEMCONV_STABILITY_OPT_IN. Having something like this for messaging (say messaging_latest_experimental) would
- give us a way forward to update outdated instrumentations to the latest Semantic Conventions without immediately breaking users that rely on the old behavior
- help clearly communicate that breaking changes are expected when this value is set, helping with future updates until the messaging semantic conventions are stable.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Metadata
Metadata
Assignees
Type
Projects
Status
Status