Capture an error when a transaction is rejected due to being invalid

[the21st]

Problem Statement

Whenever a transaction grows too large, it gets discarded due to being Invalid, since it exceeded the size limit. Currently there's no mechanism that would inform us engineers that this happened.

Solution Brainstorm

Sentry could automatically capture an error in such case, so that we engineers know about this invalid transaction and can fix it.

Product Area

Performance

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

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

[bcoe]

Hello @the21st, what SDK are you using that you're running into these size limits with?

[the21st]

@bcoe we're using the Python SDK. We're running into limits when e.g. we fire a lot of SQL queries (think 400+) within a single transaction. These queries are auto-instrumented as spans by the Sentry SDK automatically.

[sentrivana]

Hey @the21st, I'm wondering whether this pops up in your logs? We should be logging an error in the SDK if we receive a reply with a non-200 status code when sending an event to Sentry. (I believe the server would reply with a 400 in case the payload is too big.) That'd be one place to look.

You might also be able to see some stats on dropped transactions on the Stats page in the UI.

[the21st]

@sentrivana what should I search for in our logs? I'll take a look.

As for the stats page - yes, I see it there, but that cannot be alerted on, and doesn't give us almost any debugging info for that dropped transaction.

[szokeasaurusrex]

what should I search for in our logs? I'll take a look.

@the21st logs from the Sentry SDK should be prefixed with [sentry].