Insights into why Errors are Dropped

[kpujjigit]

Problem Statement

On the topic of rate-limiting, filtering, spike protection and spend allocation, interests have been expressed to:

• Get a view into why specific errors get dropped (Similar to our internal Admin tool metrics)
• Get better insights into the frequency of deleted/discarded issues.

Solution Brainstorm

This could be a report customers run. Or..

Add reasons for dropping events in the Stats page, much like our internal admin metrics, where hovering over a timeframe can drill into reasons for dropping:

Provide counts of deleted/discarded Errors within Project Settings > Inbound Filters:

Share details on which issues are rate limited within Project Settings > Client Keys (DSN) > Configure (Probably not possible since this info is filtered at the ingestion layer):

Product Area

Stats

[getsantry[bot]]

Assigning to @getsentry/support for routing ⏲️

[getsantry[bot]]

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

[Dhrumil-Sentry]

This is a valid ask and I will link some other related issues pertaining to the org stats here. We'll add this to the backlog and I'll update the issue when we have a timeline

[realkosty]

@Dhrumil-Sentry duplicate of https://github.com/getsentry/sentry/issues/44875 ?

[Dhrumil-Sentry]

@realkosty yes this is a duplicate of the issue you linked, Closing this one as a duplicate

[mrduncan]

@priscilawebdev I think your recent stats improvements resolved this?