Flexible email 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 have multiple features related to email alerting that together allow to create regular reports for different teams working on a single big application.
- Scheduling, so that reports can be sent daily, weekly, bi-weekly and so on.
Ideally this should be a cron-like configuration.
- Dynamic routing logic for alerts, so that errors that are assigned to a particular team are sent to this particular team.
Such logic needs to be simple to define for all teams altogether, without the need to maintain a list of teams, a lot of IF-THEN conditions, and especially without the need to make multiple alert configurations. In Sentry each team has information associated with it, e.g. a team email address, so when getting errors for a particular assigned team, it's email can be used.
- Aggregation of errors for a specific period of time that need to be included in such a report.
Let's say we need a weekly report:
- we might want to notify the team about all errors assigned to it that happened between last report time and current time
- or we might need to send information about all errors that are still open at the moment
Solution Brainstorm
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
The issue names no files, tests, or entry points. Start by reviewing the Alerts product area and current email-alert capabilities, then clarify whether scheduling, dynamic routing, aggregation, or all three are in scope. Done criteria would need to specify the supported configuration and report behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100