-
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
Capture custom HTTP headers (Part 2) #681
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Varsha GS <[email protected]>
Signed-off-by: Varsha GS <[email protected]>
Signed-off-by: Varsha GS <[email protected]>
Signed-off-by: Varsha GS <[email protected]>
f2086c7
to
0b0fbf6
Compare
0b0fbf6
to
7c69cd8
Compare
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.
Nice refactor @GSVarsha!
I have a few change requests, and I think you should also extend the test_extract_custom_headers
in the test_traceutils.py
file to cover all the types of headers supported now.
Signed-off-by: Varsha GS <[email protected]>
7c69cd8
to
51c705c
Compare
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.
Capture custom HTTP headers (Part 2)
What?
aiohttp-client: 🟨 requestHeadersOnExitSpans
aiohttp-server: 🟨 responseHeadersOnEntrySpans
tornado-client: 🟥 requestHeadersOnExitSpans, responseHeadersOnExitSpans
wsgi: 🟨 responseHeadersOnEntrySpans
flask: 🟨 (needs request header testcase)
starlette: 🟨 (needs response header testcase)
Enhancement
Use a single common method to capture custom headers.