Event Exclusion Capability for Sentry Crash Dashboard

[MercuryLiRC]

Problem Statement

In our current use of Sentry, we've encountered instances where the crash dashboard includes all reported events, leading to skewed crash rate metrics. For example, non-critical events are being counted alongside critical ones, which inflates the crash rates and hinders our ability to accurately measure and respond to application stability. This impacts our decision-making and resource allocation as the crash rate is a key performance indicator for our application's health.

Solution Brainstorm

Event Exclusion: Introduce a feature that allows users to create exclusion rules for events that should not impact the crash rate statistics. This could be based on error severity, tags, or frequency of occurrence.

Advanced Filtering in Dashboard: Implement an advanced filtering system within the crash dashboard that allows for real-time adjustments to what is displayed, such as toggles or checkboxes to include or exclude event categories.

┆Issue is synchronized with this Jira Improvement by Unito

[AbhiPrasad]

@MercuryLiRC thanks for writing in! I'm going to transfer this to the main Sentry repo to be triaged as this requires more than SDK changes to get working.

[getsantry[bot]]

Assigning to @getsentry/support for routing ⏲️

[getsantry[bot]]

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

[k-fish]

Hey there @MercuryLiRC, are you talking about a dashboard setup for your org under Dashboards in your sidebar? If so could you let me know the dashboard id (in the url)

[AlbertInRC]

Hi @k-fish ,

This is Albert Gu. I contacted Sentry support team.

Current issue:

• Sentry's crash free sessions rate will count the unhandled errors even after we filter out the errors on the project settings.

Our requirement:

• Provide us a way to stop counting the filtered unhandled Sentry errors in calculating the crash free sessions rate.

[AlbertInRC]

For some known but not harmful unhandled Sentry errors, we shouldn't count them in the crash free sessions rate from our perspective.

[getsantry[bot]]

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

[k-fish]

Hey @AlbertInRC , was there someone in support you were already talking to, so I can follow up with them? It sounds like you want to change how the crash free rate is calculated (by not including the errors), and aren't having issues with dashboards themselves (cc: @getsentry/telemetry-experience)

[AlbertInRC]

Hi @k-fish , Your understanding is correct. It's not about the dashboards themselves. I have been talking with Gideon Lapshun and you could align with him. Thank you

[getsantry[bot]]

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

[getsantry[bot]]

Routing to @getsentry/product-owners-ingestion-and-filtering for triage ⏲️

[iker-barriocanal]

I'll bring this with the team next week, we'll keep the ticket up-to-date.

[olksdr]

@matejminar Hey, is this something your team can pick up and look into?

[getsantry[bot]]

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

[Dhrumil-Sentry]

Thanks for this feedback, We'll add this to our backlog but we have no plans to work on this in the next few months at least

[tsalikismarshmallow]

Thanks for this feedback, We'll add this to our backlog but we have no plans to work on this in the next few months at least

Hello, do you have an update or approximate ETA of when you'll pick this up?

[rachrwang]

We don't have an ETA for this ticket at the moment, will update this ticket if we do