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 upOption to disable alert sending for x seconds after startup. #2592
Comments
This comment has been minimized.
This comment has been minimized.
|
Related: #422 (comment) |
This comment has been minimized.
This comment has been minimized.
|
This is one of the things a FOR clause protects against which ~all alerts should have, other considerations are already in #422. |
brian-brazil
closed this
Apr 6, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 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. |
lock
bot
locked and limited conversation to collaborators
Mar 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
liquidgecka commentedApr 6, 2017
When prometheus is configured with alerts in the form:
up{job="example"} > 5a restart can cause prometheus to actually sent alerts because it doesn't have recent data from those metrics, even though the next collection will actually report them up and resolve the alert. What I would love is a configuration option to either allow alerting to be delayed until each source has been queried x times, or to delay alert sending for x seconds on startup. This would allow the state to become stable before sending me a dozen pages that get immediately cleared.