prometheus / prometheus/alertmanager
Silence notifications
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
If a silence expires and the root cause that triggered the alert is not yet resolved, it can generate confusion when the alert starts firing. This can be particularly frustrating if an alert becomes unsilenced over a weekend or if the person that originally silenced the alert is on vacation.
I would find it useful if Alertmanager could send a notification when:
a) silences are created (e.g. so they show up in Slack/HipChat)
b) silences have just expired (which helps explain why the alerts start firing again)
You could take this one step further by sending 'silence reminders' to the silence author, for example on a Friday before the weekend if the silence would expire over the weekend.
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
No files, tests, or entry points are named in the issue. First clarify whether the scope is notifications for silence creation, expiration, reminders, or all three, then locate the relevant silence and notification flows in Alertmanager. Done should include agreed behavior and tests covering the selected notification cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100