github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2025-01-10 15:14:09 +00:00
Code Issues Projects Releases Packages Wiki Activity

vmalert: add info about search.latencyOffset to Troubleshooting (#3151)

Browse source 
Signed-off-by: hagen1778 <roman@victoriametrics.com>
This commit is contained in:
Roman Khavronenko 2022-09-23 09:49:14 +02:00 committed by GitHub
parent fc9caa6738
commit 7748a9d629
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
app/vmalert/README.md
View file

@ -650,6 +650,10 @@ may get empty response from datasource and produce empty recording rules or rese
<img alt="vmalert evaluation when data is delayed" src="vmalert_ts_data_delay.gif">
_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

4
docs/vmalert.md
View file

@ -654,6 +654,10 @@ may get empty response from datasource and produce empty recording rules or rese
<img alt="vmalert evaluation when data is delayed" src="vmalert_ts_data_delay.gif">
_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