Correct exporter user-agent format (#3052)

open-telemetry · Jan 4, 2023 · 7e9ba16 · 7e9ba16
1 parent 23b1623
commit 7e9ba16
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -7,6 +7,9 @@ release.
 
 ## Unreleased
 
+- Remove spaces from example exporter User-Agent header to conform to RFC7231 & RFC7230.
+  [#3052](https://github.com/open-telemetry/opentelemetry-specification/pull/3052)
+
 ### Context
 
 ### Traces

diff --git a/specification/protocol/exporter.md b/specification/protocol/exporter.md
@@ -165,7 +165,7 @@ For OTLP/HTTP, the errors `408 (Request Timeout)` and `5xx (Server Errors)` are
 OpenTelemetry protocol exporters SHOULD emit a User-Agent header to at a minimum identify the exporter, the language of its implementation, and the version of the exporter. For example, the Python OTLP exporter version 1.2.3 would report the following:
 
 ```
-OTel OTLP Exporter Python/1.2.3
+OTel-OTLP-Exporter-Python/1.2.3
 ```
 
 The format of the header SHOULD follow [RFC 7231][rfc-7231]. The conventions used for specifying the OpenTelemetry SDK language and version are available in the [Resource semantic conventions][resource-semconv].