prometheus / prometheus/alertmanager
need option to fire all currently firing alerts after mute time interval is over.
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?
I have a mute time interval of 2 hours.
mute_time_intervals:
- name: maintenance-times
time_intervals:
- weekdays: ['Sunday']
- times:
- start_time: '10:00'
end_time: '12:00'
and I have a repeat_interval of 4 hours.
repeat_interval: 4h
What did you expect to see?
We need an option to fire all currently firing alerts as soon as the mute time interval complets.
What did you see instead? Under which circumstances?
firing alerts do not get fired after the mute time interval is over.
they get fired only after 4 hours.
Environment
-
System information:
Linux 3.10.0-1062.el7.x86_64 x86_64
-
Alertmanager version:
0.25.0
-
Prometheus version:
2.37.8 -
Alertmanager configuration file:
omitting irrelevant conf.
mute_time_intervals:
- name: maintenance-times
time_intervals:
- weekdays: ['Sunday']
- times:
- start_time: '10:00'
end_time: '12:00'
and I have a repeat_interval of 4 hours.
repeat_interval: 4h
- Prometheus configuration file:
Irrelevant ```
* Logs:
Irrelevant ```
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
Start by tracing how Alertmanager processes mute_time_intervals and repeat_interval for firing alerts, then reproduce the Sunday 10:00–12:00 configuration with a 4-hour repeat interval. The work is done when an explicit option causes currently firing alerts to be notified as soon as the mute interval ends, with the existing repeat behavior unchanged when the option is not enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100