getsentry / getsentry/sentry

Resolve PagerDuty Incidents automatically once Sentry alerts have been Resolved

Open
#34,372 15 comments 8 reactions 0 assignees View on GitHub
Product Area: Settings - Integrations
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

### Problem Statement

Given: a Sentry Alert rule that creates a PagerDuty Incident when the rule criteria are met.

Desired Behavior: When the Sentry Alert transitions to the **Resolved** state, the PagerDuty Incident is also updated to the **Resolved** state.

Observed Behavior: Once the Sentry Alert is created, along with the PagerDuty Incident, there is no further action taken on the PagerDuty Incident; it must be manually resolved.

### Why is this useful?

It is common for on-call engineers to configure their PagerDuty settings to only wake them up if an Incident has been open for some time, e.g. 10 minutes. This is useful to handle pages that frequently self-resolve within a few minutes, while allowing those that **don't** self-resolve to notify the on-call engineer.

### Solution Brainstorm

Add a checkbox for automatically resolving a PagerDuty Incident once the Sentry Alert that created that Incident has transitioned to the **Resolved** state. This option would probably be best presented in the Sentry Alert configuration view, rather than as a global setting in the PagerDuty Integrations view.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.