debug mode should raise (or at least warn) when span count limit is reached and when payload limit is reached as well

[pbernery]

Problem Statement

I have some transactions that embed many spans, more than 1000. I have been told that this is a limit of Sentry, and that when it happens, the server does not process those transactions. Same when the payload or when an attribute of the payload is too bug (how big, I don't know, but I have a SQL span that triggers a very big SQL INSERT, leading to this issue).

That's totally understandable, for many reasons.

However, there is something to improve. Currently, those transactions are ignored silently. This is an issue as nothing tells you if you misconfigured Sentry or if there was anything else. There is an option to enable a debug mode in Sentry Ruby, but it does not raise or warn when those limits are reached.

Solution Brainstorm

I believe:

• there should be a space in Sentry front where those issues should be presented, to help better integrate the SDK,
• the debug mode of the client SDK should raise or warn when a limit is reached.

Product Area

Performance

[getsantry]

Assigning to @getsentry/support for routing ⏲️