prometheus/rules
Julien Pivotto ce55e5074d Add 'keep_firing_for' field to alerting rules
This commit adds a new 'keep_firing_for' field to Prometheus alerting
rules. The 'resolve_delay' field specifies the minimum amount of time
that an alert should remain firing, even if the expression does not
return any results.

This feature was discussed at a previous dev summit, and it was
determined that a feature like this would be useful in order to allow
the expression time to stabilize and prevent confusing resolved messages
from being propagated through Alertmanager.

This approach is simpler than having two PromQL queries, as was
sometimes discussed, and it should be easy to implement.

This commit does not include tests for the 'resolve_delay' field.  This
is intentional, as the purpose of this commit is to gather comments on
the proposed design of the 'resolve_delay' field before implementing
tests. Once the design of the 'resolve_delay' field has been finalized,
a follow-up commit will be submitted with tests."

See https://github.com/prometheus/prometheus/issues/11570

Signed-off-by: Julien Pivotto <roidelapluie@o11y.eu>
2023-01-13 12:11:39 +01:00
..
fixtures fixes yamllint errors 2021-06-12 12:47:47 +02:00
alerting_test.go Add 'keep_firing_for' field to alerting rules 2023-01-13 12:11:39 +01:00
alerting.go Add 'keep_firing_for' field to alerting rules 2023-01-13 12:11:39 +01:00
manager_test.go Add 'keep_firing_for' field to alerting rules 2023-01-13 12:11:39 +01:00
manager.go Add 'keep_firing_for' field to alerting rules 2023-01-13 12:11:39 +01:00
recording_test.go rules: remove classic UI code (#10730) 2022-05-23 16:21:50 +02:00
recording.go Update package rules for new labels.Labels type 2022-12-19 15:22:09 +00:00