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 up[Proposal] Allow to use evaluation_interval for alert FOR calculation #4744
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
No, not really, proposal is not about alert rule testing, but about making FOR dependency on evaluation_interval more explicit. So, it would be easier to maintain alert rules after they are tested. |
This comment has been minimized.
This comment has been minimized.
|
This is more a job for your configuration management system which Prometheus doesn't attempt to replicate. |
simonpasquier
added
kind/enhancement
component/rules
labels
Oct 18, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
dmajere commentedOct 15, 2018
Allow to use evaluation_interval for alert FOR calculation
It's a common problem to find a right value for alerts FOR parameter.
In general you want your alert rule to be evaluated for N evaluation periods, so you have to manually calculate FOR: N * evaluation_interval, which is error prone due to possible changes of a prometheus server that would lead to necessity to change [possibly] every alert rule configuration.
It would be great to have an ability to specify evaluation_interval based evaluation as a value for FOR.
For example: