prometheus / prometheus/alertmanager
Feature request: Expiry for resolved alerts in long-running groups
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
What did you do?
Each time a notification is sent for an alert group, alertmanager keeps resolved alerts for that group in memory and always sends them.
What did you expect to see?
For very long-running or large groups, this means you can get continuous resolves for potentially very old alerts, long after their resolution. I keep receiving messages for something that expired a very long time ago.
Should we consider expiring resolved alerts from groups if they've been around for long enough?
Environment
n/a
- System information:
n/a
- Alertmanager version:
main
- Prometheus version:
n/a
-
Alertmanager configuration file:
n/a -
Prometheus configuration file:
n/a -
Logs:
n/a
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. Start by tracing how Alertmanager retains resolved alerts in long-running groups and how those groups are rendered for notifications; clarify the expiry policy and its interaction with deduplication before defining tests that demonstrate old resolved alerts are no longer sent.
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
- 25/100