Added note on data retention to documentation for repeat_interval (#3147)

* Added note on data retention to documentation for repeat_interval

Signed-off-by: Soon-Ping Phang <soonping@amazon.com>
---------

Signed-off-by: Soon-Ping Phang <soonping@amazon.com>
This commit is contained in:
Soon-Ping 2023-03-07 02:27:12 -08:00 committed by GitHub
parent d8bea84adc
commit 6bb49b2f1c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions

View File

@ -194,6 +194,10 @@ matchers:
# How long to wait before sending a notification again if it has already # How long to wait before sending a notification again if it has already
# been sent successfully for an alert. (Usually ~3h or more). # been sent successfully for an alert. (Usually ~3h or more).
# 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: <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