Show Issue's % Impact on the Crash Rate
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### 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
Contributor guide
Research direction
No files, tests, or entry points are identified. Start by reviewing the Issues product area and clarify whether the feature should show each issue's share of crashes or its contribution to the overall crash rate; done means the chosen metric is defined and displayed consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100