messaging: add messaging_latest_experimental opt-in value

.chloggen/feat_experimental_messaging.yaml

@@ -0,0 +1,22 @@
+# Use this changelog template to create an entry for release notes.
+#
+# If your change doesn't affect end users you should instead start
+# your pull request title with [chore] or use the "Skip Changelog" label.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: "enhancement"
+
+# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
+component: "messaging"
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Add messaging_latest_experimental feature flag to enable experimental messaging conventions"
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+# The values here must be integers.
+issues: [2928]
+
+# (Optional) One or more lines of additional information to render under the primary note.
+# These lines will be padded with 2 spaces and then inserted directly into the document.
+# Use pipe (|) for multiline entries.
+subtext:

docs/messaging/README.md

@@ -24,12 +24,17 @@ This document defines semantic conventions for messaging systems spans, metrics
 >   * `messaging` - emit the new, stable messaging conventions,
 >     and stop emitting the old experimental messaging conventions
 >     that the instrumentation emitted previously.
+>   * `messaging_latest_experimental` - emit the latest in-development messaging conventions
+>     and stop emitting the old experimental conventions (v1.24.0 or prior). If stable
+>     messaging conventions are available, emit both stable and latest in-development conventions.
 >   * `messaging/dup` - emit both the old and the stable messaging conventions,
 >     allowing for a seamless transition.
 >   * The default behavior (in the absence of one of these values) is to continue
 >     emitting whatever version of the old experimental messaging conventions
 >     the instrumentation was emitting previously.
->   * Note: `messaging/dup` has higher precedence than `messaging` in case both values are present
+>   * Notes:
+>     * `messaging/dup` has higher precedence than `messaging` in case both values are present
+>     * `messaging_latest_experimental` has higher precedence than both `messaging/dup` and `messaging`
 > * SHOULD maintain (security patching at a minimum) the existing major version
 >   for at least six months after it starts emitting both sets of conventions.
 > * SHOULD drop the environment variable in the next major version.

docs/messaging/azure-messaging.md

@@ -24,12 +24,17 @@ The Semantic Conventions for [Azure Service Bus](https://learn.microsoft.com/azu
 >   * `messaging` - emit the new, stable messaging conventions,
 >     and stop emitting the old experimental messaging conventions
 >     that the instrumentation emitted previously.
+>   * `messaging_latest_experimental` - emit the latest in-development messaging conventions
+>     and stop emitting the old experimental conventions (v1.24.0 or prior). If stable
+>     messaging conventions are available, emit both stable and latest in-development conventions.
 >   * `messaging/dup` - emit both the old and the stable messaging conventions,
 >     allowing for a seamless transition.
 >   * The default behavior (in the absence of one of these values) is to continue
 >     emitting whatever version of the old experimental messaging conventions
 >     the instrumentation was emitting previously.
->   * Note: `messaging/dup` has higher precedence than `messaging` in case both values are present
+>   * Notes:
+>     * `messaging/dup` has higher precedence than `messaging` in case both values are present
+>     * `messaging_latest_experimental` has higher precedence than both `messaging/dup` and `messaging`
 > * SHOULD maintain (security patching at a minimum) the existing major version
 >   for at least six months after it starts emitting both sets of conventions.
 > * SHOULD drop the environment variable in the next major version.

docs/messaging/gcp-pubsub.md

@@ -24,12 +24,17 @@ The Semantic Conventions for [Google Cloud Pub/Sub](https://cloud.google.com/pub
 >   * `messaging` - emit the new, stable messaging conventions,
 >     and stop emitting the old experimental messaging conventions
 >     that the instrumentation emitted previously.
+>   * `messaging_latest_experimental` - emit the latest in-development messaging conventions
+>     and stop emitting the old experimental conventions (v1.24.0 or prior). If stable
+>     messaging conventions are available, emit both stable and latest in-development conventions.
 >   * `messaging/dup` - emit both the old and the stable messaging conventions,
 >     allowing for a seamless transition.
 >   * The default behavior (in the absence of one of these values) is to continue
 >     emitting whatever version of the old experimental messaging conventions
 >     the instrumentation was emitting previously.
->   * Note: `messaging/dup` has higher precedence than `messaging` in case both values are present
+>   * Notes:
+>     * `messaging/dup` has higher precedence than `messaging` in case both values are present
+>     * `messaging_latest_experimental` has higher precedence than both `messaging/dup` and `messaging`
 > * SHOULD maintain (security patching at a minimum) the existing major version
 >   for at least six months after it starts emitting both sets of conventions.
 > * SHOULD drop the environment variable in the next major version.

docs/messaging/kafka.md

@@ -32,12 +32,17 @@ The Semantic Conventions for [Apache Kafka](https://kafka.apache.org/) extend an
 >   * `messaging` - emit the new, stable messaging conventions,
 >     and stop emitting the old experimental messaging conventions
 >     that the instrumentation emitted previously.
+>   * `messaging_latest_experimental` - emit the latest in-development messaging conventions
+>     and stop emitting the old experimental conventions (v1.24.0 or prior). If stable
+>     messaging conventions are available, emit both stable and latest in-development conventions.
 >   * `messaging/dup` - emit both the old and the stable messaging conventions,
 >     allowing for a seamless transition.
 >   * The default behavior (in the absence of one of these values) is to continue
 >     emitting whatever version of the old experimental messaging conventions
 >     the instrumentation was emitting previously.
->   * Note: `messaging/dup` has higher precedence than `messaging` in case both values are present
+>   * Notes:
+>     * `messaging/dup` has higher precedence than `messaging` in case both values are present
+>     * `messaging_latest_experimental` has higher precedence than both `messaging/dup` and `messaging`
 > * SHOULD maintain (security patching at a minimum) the existing major version
 >   for at least six months after it starts emitting both sets of conventions.
 > * SHOULD drop the environment variable in the next major version.

docs/messaging/messaging-metrics.md

@@ -34,12 +34,17 @@ linkTitle: Metrics
 >   * `messaging` - emit the new, stable messaging conventions,
 >     and stop emitting the old experimental messaging conventions
 >     that the instrumentation emitted previously.
+>   * `messaging_latest_experimental` - emit the latest in-development messaging conventions
+>     and stop emitting the old experimental conventions (v1.24.0 or prior). If stable
+>     messaging conventions are available, emit both stable and latest in-development conventions.
 >   * `messaging/dup` - emit both the old and the stable messaging conventions,
 >     allowing for a seamless transition.
 >   * The default behavior (in the absence of one of these values) is to continue
 >     emitting whatever version of the old experimental messaging conventions
 >     the instrumentation was emitting previously.
->   * Note: `messaging/dup` has higher precedence than `messaging` in case both values are present
+>   * Notes:
+>     * `messaging/dup` has higher precedence than `messaging` in case both values are present
+>     * `messaging_latest_experimental` has higher precedence than both `messaging/dup` and `messaging`
 > * SHOULD maintain (security patching at a minimum) the existing major version
 >   for at least six months after it starts emitting both sets of conventions.
 > * SHOULD drop the environment variable in the next major version.

docs/messaging/messaging-spans.md

@@ -55,12 +55,17 @@ linkTitle: Spans
 >   * `messaging` - emit the new, stable messaging conventions,
 >     and stop emitting the old experimental messaging conventions
 >     that the instrumentation emitted previously.
+>   * `messaging_latest_experimental` - emit the latest in-development messaging conventions
+>     and stop emitting the old experimental conventions (v1.24.0 or prior). If stable
+>     messaging conventions are available, emit both stable and latest in-development conventions.
 >   * `messaging/dup` - emit both the old and the stable messaging conventions,
 >     allowing for a seamless transition.
 >   * The default behavior (in the absence of one of these values) is to continue
 >     emitting whatever version of the old experimental messaging conventions
 >     the instrumentation was emitting previously.
->   * Note: `messaging/dup` has higher precedence than `messaging` in case both values are present
+>   * Notes:
+>     * `messaging/dup` has higher precedence than `messaging` in case both values are present
+>     * `messaging_latest_experimental` has higher precedence than both `messaging/dup` and `messaging`
 > * SHOULD maintain (security patching at a minimum) the existing major version
 >   for at least six months after it starts emitting both sets of conventions.
 > * SHOULD drop the environment variable in the next major version.

docs/messaging/rabbitmq.md

@@ -24,12 +24,17 @@ The Semantic Conventions for [RabbitMQ](https://www.rabbitmq.com/) extend and ov
 >   * `messaging` - emit the new, stable messaging conventions,
 >     and stop emitting the old experimental messaging conventions
 >     that the instrumentation emitted previously.
+>   * `messaging_latest_experimental` - emit the latest in-development messaging conventions
+>     and stop emitting the old experimental conventions (v1.24.0 or prior). If stable
+>     messaging conventions are available, emit both stable and latest in-development conventions.
 >   * `messaging/dup` - emit both the old and the stable messaging conventions,
 >     allowing for a seamless transition.
 >   * The default behavior (in the absence of one of these values) is to continue
 >     emitting whatever version of the old experimental messaging conventions
 >     the instrumentation was emitting previously.
->   * Note: `messaging/dup` has higher precedence than `messaging` in case both values are present
+>   * Notes:
+>     * `messaging/dup` has higher precedence than `messaging` in case both values are present
+>     * `messaging_latest_experimental` has higher precedence than both `messaging/dup` and `messaging`
 > * SHOULD maintain (security patching at a minimum) the existing major version
 >   for at least six months after it starts emitting both sets of conventions.
 > * SHOULD drop the environment variable in the next major version.

docs/messaging/rocketmq.md

@@ -24,12 +24,17 @@ The Semantic Conventions for [Apache RocketMQ](https://rocketmq.apache.org/) ext
 >   * `messaging` - emit the new, stable messaging conventions,
 >     and stop emitting the old experimental messaging conventions
 >     that the instrumentation emitted previously.
+>   * `messaging_latest_experimental` - emit the latest in-development messaging conventions
+>     and stop emitting the old experimental conventions (v1.24.0 or prior). If stable
+>     messaging conventions are available, emit both stable and latest in-development conventions.
 >   * `messaging/dup` - emit both the old and the stable messaging conventions,
 >     allowing for a seamless transition.
 >   * The default behavior (in the absence of one of these values) is to continue
 >     emitting whatever version of the old experimental messaging conventions
 >     the instrumentation was emitting previously.
->   * Note: `messaging/dup` has higher precedence than `messaging` in case both values are present
+>   * Notes:
+>     * `messaging/dup` has higher precedence than `messaging` in case both values are present
+>     * `messaging_latest_experimental` has higher precedence than both `messaging/dup` and `messaging`
 > * SHOULD maintain (security patching at a minimum) the existing major version
 >   for at least six months after it starts emitting both sets of conventions.
 > * SHOULD drop the environment variable in the next major version.