Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upThrottle resends of alerts #2585
Comments
brian-brazil
added
the
kind/enhancement
label
Apr 6, 2017
This comment has been minimized.
This comment has been minimized.
|
Generally I think that's ok, we just need to make it explicit in the documentation and make sure that the resolve timeout in the Alertmanager needs to be higher than this value. |
This comment has been minimized.
This comment has been minimized.
|
The resolve timeout is just a default, we can adjust the end time as required inside Prometheus. |
This comment has been minimized.
This comment has been minimized.
|
Yes I realize that I just meant we need to document properly what the relationship between the two is. |
brian-brazil
added
priority/P3
component/notify
labels
Jul 14, 2017
gouthamve
added
the
help wanted
label
Jan 18, 2018
This comment has been minimized.
This comment has been minimized.
|
The current ingest path in AM for alerts has pretty high lock contention, throttling resends would be |
csmarchbanks
referenced this issue
Aug 26, 2018
Merged
Throttle resends of alerts to 1 minute by default #4538
brian-brazil
closed this
in
#4538
Aug 27, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
brian-brazil commentedApr 6, 2017
We currently send alerts at every eval interval. With a 1s eval interval, this would produce a lot of traffic to the AM.
I propose we continue to send new alerts instantly, but throttle the resends to say 60s by default.