From 7748a9d629f475bce6f96d9a28ca0d0a931c6eec Mon Sep 17 00:00:00 2001 From: Roman Khavronenko Date: Fri, 23 Sep 2022 09:49:14 +0200 Subject: [PATCH] vmalert: add info about `search.latencyOffset` to Troubleshooting (#3151) Signed-off-by: hagen1778 --- app/vmalert/README.md | 4 ++++ docs/vmalert.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/app/vmalert/README.md b/app/vmalert/README.md index f268cf959f..f5b5d27513 100644 --- a/app/vmalert/README.md +++ b/app/vmalert/README.md @@ -650,6 +650,10 @@ may get empty response from datasource and produce empty recording rules or rese vmalert evaluation when data is delayed +_Please note, by default recently written datapoints to VictoriaMetrics aren't visible for queries up to 30s. +This behavior is controlled by `--search.latencyOffset` command-line flag on vmselect. Usually, this results into +a 30s shift for recording rules results._ + Try the following recommendations in such cases: * Always configure group's `evaluationInterval` to be bigger or equal to `scrape_interval` at which metrics diff --git a/docs/vmalert.md b/docs/vmalert.md index 8d6f181597..cd28c54682 100644 --- a/docs/vmalert.md +++ b/docs/vmalert.md @@ -654,6 +654,10 @@ may get empty response from datasource and produce empty recording rules or rese vmalert evaluation when data is delayed +_Please note, by default recently written datapoints to VictoriaMetrics aren't visible for queries up to 30s. +This behavior is controlled by `--search.latencyOffset` command-line flag on vmselect. Usually, this results into +a 30s shift for recording rules results._ + Try the following recommendations in such cases: * Always configure group's `evaluationInterval` to be bigger or equal to `scrape_interval` at which metrics