Permit to override default OTLP exporter headers #4634
Draft
Conversation
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
xrmx
changed the title
emdneto
reviewed
Jun 18, 2025
exporter/opentelemetry-exporter-otlp-proto-grpc/tests/test_otlp_metrics_exporter.py
Show resolved
Hide resolved
xrmx
commented
Jun 24, 2025
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 from our distro and upstream. At the moment this is not possible because exporter always override the passed headers with the default ones. Currently the HTTP exporters sets content-type and user-agent while the grpc ones just user-agent.
It was pointed out that we may not even set grpc headers correctly but on the backend we get them just fine.
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: