Fix bug in OTEL_EXPORTER_OTLP_*_PROTOCOL handling for all signals#4627
Merged
Conversation
xiang17
changed the title
nrcventura
approved these changes
Nov 21, 2025
rajkumar-rangaraj
approved these changes
Nov 21, 2025
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
6 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.
Why
Fixes #4593
Based on existing PR at #4601
GetExporterOtlpProtocolignores the more specific (priority) environment variable and does not pass the value to SDK.What
Respect the per-signal variables (
OTEL_EXPORTER_OTLP_<signal>__PROTOCOL) env vars.Log a warning and return the default HttpProtobuf option if the env vars are invalid/absent.
Tests
Checklist
CHANGELOG.mdis updated.