[Stats] Disambiguate Dropped Events vs Invalid Events

[souredoutlook]

Problem Statement

The Dropped events column on the Stats view does not align with the definition of Dropped Events in our Usage Cards from the Billing Overview view.

In the Billing Overview we differentiate Spike Protection, Over Quota and Other categories. None of these categories track invalid events like Payload Too Large or auth issues when attempting to submit events.

In the Stats page outcomes for events that are dropped to oversized 413, 401 or 403 responses are lumped in with other outcomes which causes the two Dropped event values to look incorrect or inconsistent.

Solution Brainstorm

While it is possible to inspect the relevant API responses on the stats page to disambiguate the event outcomes and clarify why the numbers are different it would be much clearer to the end user which events where Dropped due to quota based rate limiting and which events were dropped because they are invalid.

I would recommend adding a 6th column header "Invalid" in addition to Project, Total Accepted, Filtered and Dropped.

Product Area

Stats

[getsantry[bot]]

Assigning to @getsentry/support for routing ⏲️

[getsantry[bot]]

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

[sentaur-athena]

Good feedback. Adding it to the team backlog.