prometheus / prometheus/alertmanager
[FEATURE REQUEST] Alertmanager metrics for silenced alerts
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
Problem Statement
Prometheus supplies an ALERTS metric tracking the firing alerts. Alertmanager has the ability to silence metrics. But there is no metrics exposed by Alertmanager to track the alerts that are silenced.
Proposed Solution
Introduce an alertmanager metric for alerts that are being silenced. This can further be extended to other types of suppressions (inhibition rules)
Benefits
- Improved tracking of silence
- Better Auditing
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 Alertmanager's existing metrics and silence handling, then determine the metric's behavior for silenced alerts and how it could extend to inhibition rules. Done means silenced alerts are exposed for tracking and auditing, with coverage for the resulting behavior.
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
- Mostly clear
- Newbie friendliness
- 35/100