Alert Slack notifications sent out of order (Resolved arrives before Critical/Warning)
Open
Nobody has claimed this yet.
Bug
Product Area: Alerts
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- Configure an Alert with Critical, Warning, and Resolved thresholds
- Trigger the alert so that it passes through warning/critical states and quickly resolves
- Observe the order of notifications delivered to the Slack channel and thread
Expected Result
- The initial alert state (e.g., Warning or Critical) should post first as the main channel notification or top-level message.
- Subsequent state transitions (e.g., transitions between Critical/Warning and the final "Resolved" status) should follow chronologically as replies within the thread
Actual Result
- Resolved state triggers the Alert notification in Slack first. Then, Warning and Critical states appear inside the Resolved thread
Product Area
Alerts
Link
No response
DSN
No response
Version
No response
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
Start by reproducing the alert in the SaaS environment with Critical, Warning, and Resolved thresholds, then inspect the Slack channel and thread delivery sequence. The fix is complete when the initial Warning or Critical notification is the top-level message and later state transitions, including Resolved, appear chronologically as thread replies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100