Show Issue's % Impact on the Crash Rate

[thinkocapo]

Problem Statement

User doesn't want to rely on static event counts of how many times an Issue occurred.
User wants to know how much of the crash rate is due to a single issue. My understanding is that since crash rate is a 'rate' and not a count of crashes, it's not as helpful to compare the Issue's event count to.

Solution Brainstorm

Let's say you have a Crash Free Rate of 95%, and it's due to 3 Issues occurring, Issue1, Issue2, Issue3

Solution1

Show the following:
Issue1's Impact on the Crash Rate: 50% means, "half of the crashes which bring the 100% down to 95%, are from this issue"

Issue2's Impact on the Crash Rate: 25%

Issue3's Impact on the Crash Rate: 25%

Solution2

or show it this way:
Overall Crash Rate due to Issue1: 2.5%
Overall Crash Rate due to Issue2: 1.25%
Overall Crash Rate due to Issue3: 1.25%
so notice 2.5 + 1.25 + 1.25 is 5% which is the % of sessions crashing, as the Crash-Free Rate was 95%. 95+5=100.

Product Area

Issues

[linear]

ENG-5370 Show Issue's % Impact on the Crash Rate

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[roggenkemper]

Would the user want to see this information on the issue stream/details page or just wanting to see it when looking at releases to see the impact?

[thinkocapo]

@roggenkemper any of those can be helpful. The user had a dashboard widget where they were hard-coding in some values to accomplish this. I think they had a widget type of 'Errors' but that doesn't give access to crash rates or release health info, so that's why they were trying to hard-code it, just to show me how they were limited. I forget exactly what it looked like.

Imagine an issues dashboard/strema or a issues widget (dashboard widget) and you get a column telling you the percent impact it has.

If you're looking at an Individual Issue details page, I guess that could be useful too, but we were always in dashboard type of views, discussing this.