Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

correct exporter user-agent example #3052

Merged
merged 3 commits into from
Jan 4, 2023
Merged

correct exporter user-agent example #3052

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c16007c
correct exporter user-agent example
robbkidd Dec 20, 2022
a331eba
update CHANGELOG for User-Agent correction
robbkidd Dec 21, 2022
9533b7c
Merge branch 'main' into patch-1
carlosalberto Jan 4, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion specification/protocol/exporter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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].
Expand Down