From a29c1d3a02be391ac233e00d93332741809e1221 Mon Sep 17 00:00:00 2001 From: Roman Khavronenko Date: Tue, 21 Feb 2023 22:16:15 +0100 Subject: [PATCH] docs: mention rules replay blogpost in vmalert docs (#3851) Signed-off-by: hagen1778 --- app/vmalert/README.md | 2 ++ docs/vmalert.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/app/vmalert/README.md b/app/vmalert/README.md index 2611f44415..617e73a758 100644 --- a/app/vmalert/README.md +++ b/app/vmalert/README.md @@ -621,6 +621,8 @@ can read the same rules configuration as normal, evaluate them on the given time results via remote write to the configured storage. vmalert supports any PromQL/MetricsQL compatible data source for backfilling. +See a blogpost about [Rules backfilling via vmalert](https://victoriametrics.com/blog/rules-replay/). + ### How it works In `replay` mode vmalert works as a cli-tool and exits immediately after work is done. diff --git a/docs/vmalert.md b/docs/vmalert.md index 3174642b33..c566abcad3 100644 --- a/docs/vmalert.md +++ b/docs/vmalert.md @@ -625,6 +625,8 @@ can read the same rules configuration as normal, evaluate them on the given time results via remote write to the configured storage. vmalert supports any PromQL/MetricsQL compatible data source for backfilling. +See a blogpost about [Rules backfilling via vmalert](https://victoriametrics.com/blog/rules-replay/). + ### How it works In `replay` mode vmalert works as a cli-tool and exits immediately after work is done.