Skip to content
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

crashpad_handler: add response body to error log if status is not OK #87

Merged
merged 1 commit into from
Jun 15, 2023

Conversation

supervacuus
Copy link
Collaborator

This is important because if the crashpad_handler receives a 400 (Bad Request) for whichever reason from relay, it will detail why in the response body. This helps identify the cause of the rejection.

I am open to suggestions for further logs if you have any, but I think this covers the most immediate needs. Everything else would require access to the minidump or envelope, right?

...in case the response status is not 200. This is
important, because if the crashpad-handler receives
an 400 (Bad Request) for whichever reason, it will
detail why in the response-body.

This helps customers and us to figure out why the
minidump endpoint negates requests from the
crashpad-handler in case this happens.
@supervacuus supervacuus requested a review from a team June 12, 2023 11:38
@supervacuus supervacuus merged commit 432ff49 into getsentry Jun 15, 2023
4 checks passed
@supervacuus supervacuus deleted the feat/crashpad_curl_response_body_log branch June 15, 2023 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants