-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pyramid: capture responseHeadersOnEntrySpans #496
Conversation
Signed-off-by: Varsha GS <[email protected]>
Signed-off-by: Varsha GS <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears that the request header capture feature, was previously implemented, but was not covered with UT.
And since this change potentially impacts that feature too, could we add coverage for that too?
Signed-off-by: Varsha GS <[email protected]>
- test(request_header_capture) Signed-off-by: Varsha GS <[email protected]>
For sure! Added coverage for capturing request headers in the latest commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me.
What
Pyramid: capture responseHeadersOnEntrySpans
Signed-off-by: Varsha GS [email protected]
References
Why
According to our spec, tracers SHOULD capture all four flavours of HTTP headers.