chore(http): captured request and response headers separately - #2680
Draft
aryamohanan wants to merge 1 commit into
Draft
chore(http): captured request and response headers separately#2680aryamohanan wants to merge 1 commit into
aryamohanan wants to merge 1 commit into
Conversation
aryamohanan
changed the title
aryamohanan
changed the title
Contributor
Author
|
This is currently blocked pending community feedback on the HTTP header mapping approach. Since this is essentially a bug fix rather than a feature, it is currently considered low priority and can be implemented in a later phase. |
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
1 participant
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.
This PR adds separate request and response HTTP header fields to HTTP spans while preserving the existing combined header field for backwards compatibility.
These fields are internal and are used only for OTLP field mapping. They are removed during transformation and are not forwarded to the backend.
ref https://jsw.ibm.com/browse/INSTA-102440