getsentry / getsentry/sentry

Configurable crash-free rate thresholds for the Releases page health indicator

Open
#119,315 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Product Area: Releases Quick Win
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Problem Statement

On the Releases list page, the crash-free-rate column shows a health indicator (fire for critical, yellow warning, green check), but the thresholds are hardcoded (fire below 98%, warning below 99.5% in releaseCardProjectRow.tsx). Teams with different reliability targets can't align it to their own goals. Crash-rate metric Alerts already let a team configure critical/warning thresholds, but those only notify whoever set them up. Customers want the passive Releases-page indicator to reflect their own target so anyone viewing a release in the UI can tell at a glance whether it's healthy.

Solution Brainstorm

Let orgs/projects configure the crash-free-rate thresholds driving the Releases-page indicator (a critical threshold for the fire icon, a target threshold for the warning icon), ideally reusing the existing Release Thresholds concept (crash_free_session_rate / crash_free_user_rate).

Product Area

Releases

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with releaseCardProjectRow.tsx to trace the hardcoded crash-free-rate thresholds and indicator states. Read the existing Release Thresholds concept and crash-rate metric Alerts to understand how crash_free_session_rate and crash_free_user_rate are configured. Done means orgs or projects can configure critical and target thresholds and the Releases-page indicator reflects them.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.