getsentry / getsentry/sentry

[Integration Platform] Deactivate Integrations with Failing Webhook Requests

Open
#86,624 3 comments 0 reactions 0 assignees View on GitHub
Feature Product Area: Settings - Integrations
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

Integrators want to limit the amount of traffic from Sentry to their webhook endpoint for installations associated with inactivate accounts in their 3rd party service

### Solution Brainstorm

Sentry doesn't currently deactivate integrations where the webhook is failing consistently automatically.
If we did make this change it would help integrators deal with unwanted ingress to their webhook endpoint more easily.

### Product Area

Settings - Developer Settings

Contributor guide

Open the contributing guide

Research direction

Start with the Problem Statement and Solution Brainstorm, then inspect the Settings - Developer Settings integration area to identify the webhook request and integration lifecycle entry points. Define how consistently failing requests are detected and how deactivation is surfaced; done means integrations for inactive third-party accounts no longer generate unwanted webhook traffic.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.