From 56a9ea37532866b43a0b7f9e7186e4af42a2f294 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Fri, 16 Dec 2022 17:20:31 -0800 Subject: [PATCH] docs/vmalert.md: mention `latency_offset` query arg, which has been added in 86dae56bd0296c32962bc84c6c6c07b124bd67f2 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3481 --- app/vmalert/README.md | 8 ++++---- docs/vmalert.md | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/app/vmalert/README.md b/app/vmalert/README.md index 072f646ab..26f954581 100644 --- a/app/vmalert/README.md +++ b/app/vmalert/README.md @@ -695,10 +695,10 @@ may get empty response from datasource and produce empty recording rules or rese vmalert evaluation when data is delayed -_By default recently written samples to VictoriaMetrics aren't visible for queries for 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. -Note that too small value passed to `-search.latencyOffset` may lead to incomplete query results._ +By default recently written samples to VictoriaMetrics aren't visible for queries for up to 30s. +This behavior is controlled by `-search.latencyOffset` command-line flag and the `latency_offset` query ag at `vmselect`. +Usually, this results into a 30s shift for recording rules results. +Note that too small value passed to `-search.latencyOffset` or to `latency_offest` query arg may lead to incomplete query results. Try the following recommendations in such cases: diff --git a/docs/vmalert.md b/docs/vmalert.md index f32eb4b3f..30c04c696 100644 --- a/docs/vmalert.md +++ b/docs/vmalert.md @@ -699,10 +699,10 @@ may get empty response from datasource and produce empty recording rules or rese vmalert evaluation when data is delayed -_By default recently written samples to VictoriaMetrics aren't visible for queries for 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. -Note that too small value passed to `-search.latencyOffset` may lead to incomplete query results._ +By default recently written samples to VictoriaMetrics aren't visible for queries for up to 30s. +This behavior is controlled by `-search.latencyOffset` command-line flag and the `latency_offset` query ag at `vmselect`. +Usually, this results into a 30s shift for recording rules results. +Note that too small value passed to `-search.latencyOffset` or to `latency_offest` query arg may lead to incomplete query results. Try the following recommendations in such cases: