Insights into why Errors are Dropped

getsentry / sentry

Developer-first error tracking and performance monitoring

https://sentry.io

Other

38.53k stars 4.12k forks source link

Insights into why Errors are Dropped #63448

Open kpujjigit opened 7 months ago

kpujjigit commented 7 months ago

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..

1. 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:

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

3. 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] commented 7 months ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 7 months ago

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

Dhrumil-Sentry commented 7 months ago

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 commented 7 months ago

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

Dhrumil-Sentry commented 7 months ago

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

mrduncan commented 1 month ago

@priscilawebdev I think your recent stats improvements resolved this?

realkosty commented 3 weeks ago

This seems like a bit of an umbrella issue:

(1) _admin-like detailed stats

Done https://sentry.io/changelog/clearer-insights-into-your-sentry-data-with-our-updated-stats-page/

(2) visibility into counts of delete & discard

duplicate of https://github.com/getsentry/sentry/issues/47755

(3) which issues are rate limited

doesn't seem well defined to me. All issues are rate limited without any special preference to certain ones. It is possible that because some issues happen more toward the end of rate limit window than others but that's probably more of an edge case and most of the time relative event counts should be preserved with active rate limits.

@kpujjigit please clarify (3) ^

priscilawebdev commented 2 weeks ago

@mrduncan Yes, the recent updates to the stats page address item 1. Users can now see the reasons why events are not accepted.