Feature Request: Introduce Code Ownership Conditions for Issue 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
Our mono-repo's CODEOWNERS file is the source of truth when it comes to determining which team is responsible for an issue. The team assignment based on the CODEOWNERS file works well, but there is currently a gap when it comes to alerting: it is not yet possible to alert a team based on the code ownership of where the error occurred.
We are currently solving this manually by replicating the team-ownership rules in our alert, e.g.:
This requires some manual effort for dozens of teams, but more importantly, it would soon get out of sync with the CODEOWNERS file.
Solution Brainstorm
This could be solved in Sentry by allowing code ownership conditions like the following:
This logic is already used for assigning issues, but here it would be transferred to alerts.
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; begin by locating the existing issue-assignment logic that uses CODEOWNERS and the alert condition implementation. Done means alerts can use code ownership to select responsible teams without manually duplicating ownership rules.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100