Per-platform crash-free rate in Release Health
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Release Health crash-free rate is reported at the project level. Customers with multi-platform releases (PC + consoles) cannot distinguish platform-specific crash-free rates in a single view without creating separate projects per platform.
- Crash-free rate in Release Health is aggregated across all sessions in a project
- No built-in per-platform breakdown within a single release
- Workaround: maintain separate Sentry projects per platform, which fragments release tracking
Add platform/environment-level crash-free rate breakdowns to the Release Health UI, allowing a single release to surface crash-free rates segmented by platform (e.g., PC, Xbox, PlayStation).
Reported by a gaming console customer (Triiodide Technologies).
Action taken on behalf of Richard Propst.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating Release Health's crash-free-rate aggregation and UI, then trace how release and platform data are represented. Done means a single release shows separate crash-free rates for PC, Xbox, and PlayStation without requiring separate projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100