getsentry / getsentry/sentry

Alerts - Need alert on Percent of sessions affected by collection of issues not just 1 issue

Open
#107,494 4 comments 0 reactions 0 assignees View on GitHub
Feature Product Area: Alerts
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

### Problem Statement

For crash alerts, percentage of sessions affected is more meaningful than raw crash counts, since session volume changes and we want to avoid count-based noise.
For example:
- Low traffic: 1,000 sessions, 10 crashes → 1% → alert should trigger
- Peak traffic: 10,000 sessions, 10 crashes → 0.1% → alert should not trigger

We want this logic to work at both levels:
- Individual crash level (available already)
- Overall crash level
It may also be useful to expose percentage of sessions affected issue count alongside percentage of sessions  affected unique users, for better visibility into user impact.

### Solution Brainstorm

_No response_

### Product Area

Alerts

Contributor guide

Open the contributing guide

Research direction

The issue names the Alerts product area but no files, tests, or entry points. First clarify the alerting design for percentage of sessions across a collection of issues, including whether issue-count and unique-user percentages are required; done criteria are not yet defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.