getsentry / getsentry/sentry

CRON monitor alerts in Slack should show resolutions

Open
#103,211 4 comments 1 reaction 0 assignees View on GitHub
Feature Product Area: Settings - Integrations Slack
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

When I read a Slack notification about a CRON monitor that timedout or was missed, I can't know the current status of this issue. Was it resolved or is this still a problem?

It's especially interesting when you only look at the Slack channel a few times a day and you have multiple CRONs that can fail. Solving this would help narrowing the down the important alerts, those that still need to be solved.

### Solution Brainstorm

The Slack integration should probably update the previous notification or post in the same thread, to notify that the CRON issue is resolved.

Sentry already published manual resolutions and reopening in the Slack thread, see:

Image

Image

### Product Area

Crons, Alerts

Contributor guide

Open the contributing guide

Research direction

Start by locating the Slack integration for CRON monitor alerts and the existing manual resolution and reopening behavior referenced in the issue. Trace how timeout and missed notifications are posted, then determine how a resolved status should appear in the original message or thread. Done means Slack recipients can identify when a CRON alert has been resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, devops, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.