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

Sentry does not show the request body was truncated #73629

Open
cedric-spinergie opened this issue Jul 2, 2024 · 2 comments
Open

Sentry does not show the request body was truncated #73629

cedric-spinergie opened this issue Jul 2, 2024 · 2 comments

Comments

@cedric-spinergie
Copy link

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

See this issue for my initial report.

When using a SDK related to an API, send a POST request with a big request body and make it so the endpoint throws an exception. (Mine was 40kB when testing)
Configure the SDK so it automatically picks up the exception and its context (including the request body) and sends the data to Sentry.

Expected Result

I expected the body to be available on Sentry without truncation OR with clearly stated truncation.

Actual Result

Sentry has truncated the test JSON in such a way that the body field is perfectly valid and correct JSON. This is a problem because users don't know whether the data is right or wrong and they might end up debugging a non-existent problem.

In my specific tests, Sentry truncated a json array from 5XXX elements to 13XX elements. This was done silently and the resulting body field looks like perfectly valid json which is very confusing for users.

Product Area

Issues

Link

No response

DSN

No response

Version

No response

@getsantry
Copy link
Contributor

getsantry bot commented Jul 2, 2024

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

@roggenkemper
Copy link
Member

Thanks for the feedback! We have similar feedback that is already on our backlog (#68426) about being showing an indicator when the data is truncated, but having more info about people encountering this is useful. not sure when the team will work on this, but ill add this to our backlog as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants