[chore] allow category-specific values in OTEL_SEMCONV_STABILITY_OPT_IN (#2158)

This commit is contained in:
Preston Vasquez 2025-04-22 12:05:57 -06:00 committed by GitHub
parent 69fae2852c
commit 5e932efbfc
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
16 changed files with 32 additions and 32 deletions

View File

@ -20,8 +20,8 @@ database metrics and logs.
> Conventions include, but are not limited to, attributes,
> metric and span names, and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> in the existing major version as a comma-separated list of category-specific values
> (e.g., http, databases, messaging). The list of values includes:
> * `database` - emit the new, stable database conventions,
> and stop emitting the old experimental database conventions
> that the instrumentation emitted previously.

View File

@ -37,8 +37,8 @@ linkTitle: Metrics
> Conventions include, but are not limited to, attributes,
> metric and span names, and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> in the existing major version as a comma-separated list of category-specific values
> (e.g., http, databases, messaging). The list of values includes:
> * `database` - emit the new, stable database conventions,
> and stop emitting the old experimental database conventions
> that the instrumentation emitted previously.

View File

@ -28,8 +28,8 @@ linkTitle: Spans
> Conventions include, but are not limited to, attributes,
> metric and span names, and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> in the existing major version as a comma-separated list of category-specific values
> (e.g., http, databases, messaging). The list of values includes:
> * `database` - emit the new, stable database conventions,
> and stop emitting the old experimental database conventions
> that the instrumentation emitted previously.

View File

@ -21,8 +21,8 @@ and various HTTP versions like 1.1, 2 and SPDY.
> in HTTP instrumentations). Conventions include, but are not limited to, attributes,
> metric and span names, and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The only values defined so far are:
> in the existing major version as a comma-separated list of category-specific values
> (e.g., http, databases, messaging). The list of values includes:
> * `http` - emit the new, stable HTTP and networking conventions,
> and stop emitting the old experimental HTTP and networking conventions
> that the instrumentation emitted previously.

View File

@ -40,8 +40,8 @@ operations. By adding HTTP attributes to metric events it allows for finely tune
> in HTTP instrumentations). Conventions include, but are not limited to, attributes,
> metric and span names, and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The only values defined so far are:
> in the existing major version as a comma-separated list of category-specific values
> (e.g., http, databases, messaging). The list of values includes:
> * `http` - emit the new, stable HTTP and networking conventions,
> and stop emitting the old experimental HTTP and networking conventions
> that the instrumentation emitted previously.

View File

@ -45,8 +45,8 @@ and various HTTP versions like 1.1, 2 and SPDY.
> in HTTP instrumentations). Conventions include, but are not limited to, attributes,
> metric and span names, and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The only values defined so far are:
> in the existing major version as a comma-separated list of category-specific values
> (e.g., http, databases, messaging). The list of values includes:
> * `http` - emit the new, stable HTTP and networking conventions,
> and stop emitting the old experimental HTTP and networking conventions
> that the instrumentation emitted previously.

View File

@ -19,8 +19,8 @@ This document defines semantic conventions for messaging systems spans, metrics
> Conventions include, but are not limited to, attributes,
> metric and span names, span kind and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> 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,
> and stop emitting the old experimental messaging conventions
> that the instrumentation emitted previously.

View File

@ -19,8 +19,8 @@ The Semantic Conventions for [Azure Service Bus](https://learn.microsoft.com/azu
> Conventions include, but are not limited to, attributes,
> metric and span names, span kind and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> 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,
> and stop emitting the old experimental messaging conventions
> that the instrumentation emitted previously.

View File

@ -19,8 +19,8 @@ The Semantic Conventions for [Google Cloud Pub/Sub](https://cloud.google.com/pub
> Conventions include, but are not limited to, attributes,
> metric and span names, span kind and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> 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,
> and stop emitting the old experimental messaging conventions
> that the instrumentation emitted previously.

View File

@ -27,8 +27,8 @@ The Semantic Conventions for [Apache Kafka](https://kafka.apache.org/) extend an
> Conventions include, but are not limited to, attributes,
> metric and span names, span kind and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> 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,
> and stop emitting the old experimental messaging conventions
> that the instrumentation emitted previously.

View File

@ -29,8 +29,8 @@ linkTitle: Metrics
> Conventions include, but are not limited to, attributes,
> metric and span names, span kind and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> 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,
> and stop emitting the old experimental messaging conventions
> that the instrumentation emitted previously.

View File

@ -50,8 +50,8 @@ linkTitle: Spans
> Conventions include, but are not limited to, attributes,
> metric and span names, span kind and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> 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,
> and stop emitting the old experimental messaging conventions
> that the instrumentation emitted previously.

View File

@ -19,8 +19,8 @@ The Semantic Conventions for [RabbitMQ](https://www.rabbitmq.com/) extend and ov
> Conventions include, but are not limited to, attributes,
> metric and span names, span kind and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> 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,
> and stop emitting the old experimental messaging conventions
> that the instrumentation emitted previously.

View File

@ -19,8 +19,8 @@ The Semantic Conventions for [Apache RocketMQ](https://rocketmq.apache.org/) ext
> Conventions include, but are not limited to, attributes,
> metric and span names, span kind and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The list of values includes:
> 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,
> and stop emitting the old experimental messaging conventions
> that the instrumentation emitted previously.

View File

@ -44,8 +44,8 @@ metrics can be filtered for finer grain analysis.
> in RPC instrumentations). Conventions include, but are not limited to, attributes,
> metric and span names, and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The only values defined so far are:
> in the existing major version as a comma-separated list of category-specific values
> (e.g., http, databases, messaging). The list of values includes:
> * `http` - emit the new, stable networking conventions,
> and stop emitting the old experimental networking conventions
> that the instrumentation emitted previously.

View File

@ -34,8 +34,8 @@ This document defines how to describe remote procedure calls
> in RPC instrumentations). Conventions include, but are not limited to, attributes,
> metric and span names, and unit of measure.
> * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN`
> in the existing major version which is a comma-separated list of values.
> The only values defined so far are:
> in the existing major version as a comma-separated list of category-specific values
> (e.g., http, databases, messaging). The list of values includes:
> * `http` - emit the new, stable networking conventions,
> and stop emitting the old experimental networking conventions
> that the instrumentation emitted previously.