No-op: Otel headers as string already addressed by #3338#3353
Closed
No-op: Otel headers as string already addressed by #3338#3353
Conversation
Copilot
AI
changed the title
[WIP] Add support for Otel headers as string format
No-op: Otel headers as string already addressed by #3338
Apr 8, 2026
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
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.
Issue requested support for OpenTelemetry headers as a string instead of an object. This was already implemented and merged in PR #3338 ("Update OTLP headers to accept string format (spec v1.13.0)") on April 7, 2026.
PR #3338 changed:
TracingConfig.Headers/StdinOpenTelemetryConfig.Headers:map[string]string→stringparseOTLPHeaders()to parse"key=value,key=value"at export timetype: objecttotype: stringNo additional changes needed. This PR can be closed.