Support flexible email and webhook alert destinations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Organizations using custom ticketing or paging systems need a way to route Sentry alerts without relying on a supported third-party integration. Slack may be available but is not always treated as a paging endpoint, while creating a dedicated Sentry user for an email alias may be incompatible with SAML-enforced provisioning.
The requested capability is a flexible email or webhook-style alert destination that can target an external operational system. Without one, organizations must build and maintain a custom Sentry integration before adopting alerts broadly.
Related requests:
- #1617 covers arbitrary email recipients and mailing lists; it was closed due to staleness.
- #9206 covers customizable webhook payloads and was closed with an internal integration as the recommended path.
- #32313 is an open, destination-specific webhook request for Mattermost.
via anthony.yiannakou.
--
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
No implementation files, tests, or entry points are named. Start by comparing the requirements and outcomes in related issues #1617, #9206, and #32313, then establish the scope for flexible email or webhook destinations and their payload behavior. Done means an external operational system can receive Sentry alerts without a dedicated custom integration.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100