getsentry / getsentry/sentry

Alert configuration for already existing high-priority issues

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

Description

### Use case

We want to be alerted when the issue is seen more than 5 times in 15 minutes for **high priority issues**.

### Problem

With the current alert configuration options, it is not possible to have alerts for such a use case.
We can set the alert configuration to be as follows:

Image

But this creates unnecessary noise as it will also trigger alerts for issues of lower priority.

### Solution Brainstorm

- Add possibility to configure alerts based on the issue priority

### Product Area

Alerts

Contributor guide

Open the contributing guide

Research direction

Begin with the existing alert configuration and the Alerts product area; verify how issue priority and the “seen more than 5 times in 15 minutes” condition are represented. Done means an alert can target high-priority issues without notifying for lower-priority issues, with coverage for the described scenario.

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
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.