getsentry / getsentry/sentry

Muted alert started to send notifications to Slack

Open
#98,523 3 comments 0 reactions 0 assignees View on GitHub
Alerts
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

1. Create an Issue Alert that sends Slack notifications on every new issue
2. Mute the alert
3. Wait a month (I hate how non-reproducible it is, I'm so sorry, but this is what happens to us)

Note: These issues are not new at all. The Sentry project has been creating and updating issues constantly all this time- it's just now that the alert started to trigger, and send notifications to Slack

Image

Image

### Expected Result

The alert doesn't send any notifications for as long as it stays muted

### Actual Result

We started to get Slack notifications out of the blue. Luckily it's an internal testing channel and it's not bothering the developers yet :)

Unmuting it and muting it again seems to have stopped them from coming, but I thought it's worth to report what happened either way.

Image

### Product Area

Alerts

### Link

_No response_

### DSN

_No response_

### Version

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the Issue Alert mute/unmute flow and the Slack notification delivery path described in the reproduction steps. Try to reproduce the delayed notification behavior, then verify that a muted alert suppresses Slack notifications while it remains muted and that the existing regression behavior is covered by a test.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.