SDK truncation logic

[kahest]

Review implementation for any truncation of event data (e.g., error titles, stack frames, local variables). Remove truncation where possible so that Relay handles length limits and marks truncated content clearly for users.

• Keep only essential truncation needed to prevent issues e.g. such as infinite or near-infinite recursion if applicable
• Verify Relay’s configured limits before making changes, and test to ensure ingestion works as expected (exception type field example)

In scope: any code paths where data is shortened in a way that hides useful information for debugging

Out of scope: Limits explicitly decided in the past (e.g., 1000 spans per transaction, max breadcrumbs, request body truncation).

See also: https://develop.sentry.dev/sdk/data-model/envelopes/#size-limits

[linear]

CAPA-39 SDK truncation logicc

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀