prometheus / prometheus/alertmanager
Inhibits should be per-route rather than global
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
Inhibits have the potential for accidentally affecting far more alerts than is desired, particularly in environments where more than one team is sharing the alertmanager (and we'll ultimately encourage one set of alertmanagers per company).
Accordingly it'll be safer for inhibitions to be per-route, and likely also easier to work with.
Contributor guide
No contributing guide indexed for this repository
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. First clarify how inhibitions should interact with routes and identify the affected routing and inhibition components; done means inhibitions are scoped per route without unintentionally affecting unrelated alerts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100