Permit to override default OTLP HTTP exporter headers#4634
Merged
xrmx merged 5 commits intoopen-telemetry:mainfrom Aug 29, 2025
Merged
Permit to override default OTLP HTTP exporter headers#4634xrmx merged 5 commits intoopen-telemetry:mainfrom
xrmx merged 5 commits intoopen-telemetry:mainfrom
Conversation
xrmx
changed the title
emdneto
reviewed
Jun 18, 2025
xrmx
commented
Jun 24, 2025
Contributor
Author
There was a problem hiding this comment.
Wondering if instead of that we should make the default headers substituted via an entry point (or even make them a param for the init functions called by _initialize_components) so that we have a different mechanism that the user cannot easily override. This is because otherwise users setting OTEL_EXPORTER_OTLP_HEADERS will always override what distro sets.
xrmx
moved this from Ready for review
to Reviewed PR that needs fixing
in Python PR digest
xrmx
changed the title
xrmx
force-pushed
the
override-exporter-headers
branch
from
dadd176 to
6f3b497
Compare
xrmx
moved this from Reviewed PR that needs fixing
to Ready for review
in Python PR digest
xrmx
force-pushed
the
override-exporter-headers
branch
from
6f3b497 to
68776af
Compare
Contributor
Author
|
So this updates the otlp http exporters to match what the grpc ones are doing wrt channel_options that is that users are able to override the defaults but not remove them. |
Contributor
Author
|
Related to this the specs is being updated for allowing the update of users of the user agent: open-telemetry/opentelemetry-specification#4560 |
tammy-baylis-swi
approved these changes
Aug 28, 2025
emdneto
approved these changes
Aug 29, 2025
github-project-automation
bot
moved this from Ready for review
to Done
in Python PR digest
JWinermaSplunk
pushed a commit
to JWinermaSplunk/opentelemetry-python
that referenced
this pull request
Feb 17, 2026
…#4634) * opentelemetry-exporter-otlp-proto-http: permit to override default exporter headers * Add changelog --------- Co-authored-by: Tammy Baylis <[email protected]>
JWinermaSplunk
pushed a commit
to JWinermaSplunk/opentelemetry-python
that referenced
this pull request
Feb 17, 2026
…#4634) * opentelemetry-exporter-otlp-proto-http: permit to override default exporter headers * Add changelog --------- Co-authored-by: Tammy Baylis <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
We would like being able to use a specific user agent on our distro in order to discriminate OTLP traffic between our distro and upstream. At the moment this is not possible because HTTP exporters always override the passed headers with the default ones.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Does This PR Require a Contrib Repo Change?
Checklist: