search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
39.16k stars 4.2k forks source link

Indicate that variables have been truncated #73993

Open InterstellarStella opened 4 months ago

InterstellarStella commented 4 months ago

Problem Statement

On an event with local variables, there is a total size limit on all vars per frame of 2048 bytes and a maximum depth of 5. This can lead to data being truncated, but there is no information on the UI indicating that this has happened. Only Relay exposes this information in the event's JSON.

For example here this local variable has 10 entries:

Screenshot 2024-07-09 at 07 27 12

While in the JSON we see that there were 12 entries originally:

Screenshot 2024-07-09 at 07 31 46

Not knowing that there was originally more data that has been truncated can be misleading and confusing when trying to debug an error.

Solution Brainstorm

Indicate in the UI that data truncation has taken place. This could be a ... after the last entry.

Product Area

Issues

getsantry[bot] commented 4 months ago

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

getsantry[bot] commented 4 months ago

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

snigdhas commented 4 months ago

sounds like a worthwhile UI improvement, added to the Issues backlog