From 81299855d622218e5f7fc73a6bbcce814b1c1c34 Mon Sep 17 00:00:00 2001 From: George Robinson Date: Mon, 9 Oct 2023 20:38:26 +0100 Subject: [PATCH] Update configuration docs for Repeat interval Although it is true that Repeat interval should be greater than or equal to the Group interval, it should also be a multiple of it too. If the Repeat interval is not a multiple, then because of how aggregation groups are flushed, it will be made into one implicitly. This commit documents this behavior. Signed-off-by: George Robinson --- docs/configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration.md b/docs/configuration.md index 13bc3bc4c8..f084805c1d 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -200,7 +200,7 @@ matchers: # Note that this parameter is implicitly bound by Alertmanager's # `--data.retention` configuration flag. Notifications will be resent after either # repeat_interval or the data retention period have passed, whichever -# occurs first. `repeat_interval` should not be less than `group_interval`. +# occurs first. `repeat_interval` should be a multiple of `group_interval`. [ repeat_interval: | default = 4h ] # Times when the route should be muted. These must match the name of a