getsentry / getsentry/sentry

Alert Rule Backup and Restore / Version History

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

Description

### Problem Statement

When alert rules are accidentally deleted or edited, there is no way to recover them. There is no backup, versioning, or soft-delete mechanism for alert rule configurations. Recovery currently requires an ad-hoc engineering effort to pull data from the database before it's permanently removed.

### Solution Brainstorm

- Soft-delete with a retention window (e.g. 30 days) so deleted alert rules can be restored
- Version history for alert rules
- A "trash" or "recently deleted" section in the Alerts UI where deleted rules can be recovered

### Product Area

Alerts

Contributor guide

Open the contributing guide

Research direction

Start by mapping the alert-rule persistence area and the Alerts UI; the issue names no files, tests, or entry points. Compare the proposed soft-delete, retention, version-history, and recovery options with existing alert behavior. Done requires an agreed design and defined implementation scope, which this issue does not yet provide.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.