From 43a1f5658905cecd53c9da344dea602f5f3c0c46 Mon Sep 17 00:00:00 2001 From: Gustavo Vargas Date: Thu, 10 Jul 2025 16:55:31 -0600 Subject: [PATCH] Clarify protocol defaults on specification --- specification/protocol/exporter.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/specification/protocol/exporter.md b/specification/protocol/exporter.md index 5b43d66bdef..b727289c781 100644 --- a/specification/protocol/exporter.md +++ b/specification/protocol/exporter.md @@ -70,7 +70,7 @@ Each configuration option MUST be overridable by a signal specific option. - **Protocol**: The transport protocol. Options MUST be one of: `grpc`, `http/protobuf`, `http/json`. See [Specify Protocol](./exporter.md#specify-protocol) for more details. - - Default: `http/protobuf` + - Default: `http/protobuf` [4] - Env vars: `OTEL_EXPORTER_OTLP_PROTOCOL` `OTEL_EXPORTER_OTLP_TRACES_PROTOCOL` `OTEL_EXPORTER_OTLP_METRICS_PROTOCOL` `OTEL_EXPORTER_OTLP_LOGS_PROTOCOL` - Type: [Enum][] @@ -86,6 +86,8 @@ they SHOULD continue to be supported as they were part of a stable release of th most useful among the supported options. This is especially important in the presence of technical constraints, e.g. directly sending telemetry data from mobile devices to backend servers. +**[4]**: The default protocol SHOULD be `http/protobuf`, unless there are strong reasons for SDKs to select `grpc` as the default. For instance, maintaining backward compatibility may require keeping `grpc` as the default if it was previously established in a stable SDK release. + Supported values for `OTEL_EXPORTER_OTLP_*COMPRESSION` options: - `none` if compression is disabled.