prometheus / prometheus/alertmanager
Auto expire silences that don't match anything for N period
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
Proposal
Scenario: you silence something, the silence works as expected, then the alert is resolved.
Now silence matches nothing, but still stays
Suggestion: when you create a silence - there is a duration property, that specifies: "If a silence hasn't been matching anything for duration of N - auto-expire it".
This would greatly help in managing silences overall.
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. Start by locating silence creation, duration handling, and matching lifecycle code, then clarify how an inactivity period should be represented and evaluated; done means an unmatched silence expires after the configured period without affecting matching silences.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100