Allow customizing notifications for Metric Alerts
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
I want to link a playbook to the firing notifications of a metric alert. For issue alerts, I can customize the slack messages for example with a notes field where I can do this.
With metric alerts, none of the notification destinations allow specifying any context here, and the alert doesn't have a free form description either.
This essentially makes it impossible to have a metric alert used to notify teams that are not already intimately familiar with the details of how Sentry is integrated into their organization (eg, a product team vs the infrastructure team owning the Sentry deployment)
Solution Brainstorm
Add more custom fields to the actions for metric alerts, similar to Issue Alerts. For example, for email, add a notes field here. Same for Slack:
Product Area
Alerts
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
Start by comparing metric alert notification actions with the issue alert Slack and email customization described in the issue. Confirm the intended custom fields and affected notification destinations with maintainers; done means metric-alert notifications can carry playbook context for the requested destinations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100