Update configuration docs for Repeat interval (#3552)

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 <george.robinson@grafana.com>
This commit is contained in:
George Robinson 2023-10-12 16:12:12 +01:00 committed by GitHub
parent d7b865d6cc
commit 573e2c3694
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions

View File

@ -200,7 +200,7 @@ matchers:
# Note that this parameter is implicitly bound by Alertmanager's # Note that this parameter is implicitly bound by Alertmanager's
# `--data.retention` configuration flag. Notifications will be resent after either # `--data.retention` configuration flag. Notifications will be resent after either
# repeat_interval or the data retention period have passed, whichever # 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: <duration> | default = 4h ] [ repeat_interval: <duration> | default = 4h ]
# Times when the route should be muted. These must match the name of a # Times when the route should be muted. These must match the name of a