-
Notifications
You must be signed in to change notification settings - Fork 922
feat(exporters): add user-agent enrichment #4560
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.
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
base: main
Are you sure you want to change the base?
feat(exporters): add user-agent enrichment #4560
Conversation
specification/protocol/exporter.md
Outdated
@@ -208,6 +208,21 @@ 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]. | |||
|
|||
Exporters MAY expose a configuration option to append a product identifier to the User-Agent | |||
header as defined in [RFC 7231][rfc-7231]. Such option should not be available as |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SHOULD NOT
(even MUST NOT
?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with MUST NOT
. Thanks @carlosalberto :)
commit d7d96d7
Maybe Collector folks should review this too @mx-psi ? |
My understanding is that Collector components are not, as a general rule, bound by the spec. I guess we can add this to our coding guidelines in the Collector as well if it gets approved here to make sure it is followed |
…telemetry-specification into enrich-user-agent-header
Fixes #4479
Changes
Document that exporters may allow a
user-agent
option to append a product identifier to the exporter User Agent header. such option is only available via local var (not environment)For non-trivial changes, follow the change proposal process.
CHANGELOG.md
file updated for non-trivial changesspec-compliance-matrix.md
updated if necessary