docs/troubleshooting: mention query latency in unexpected query results

See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5555

Signed-off-by: hagen1778 <roman@victoriametrics.com>
This commit is contained in:
hagen1778 2024-01-17 11:59:14 +01:00 committed by Aliaksandr Valialkin
parent 36e7689946
commit d4ae2cb5d0
No known key found for this signature in database
GPG key ID: 52C003EE2BCDB9EB

View file

@ -179,6 +179,9 @@ If you see unexpected or unreliable query results from VictoriaMetrics, then try
to the static interval for gaps filling by setting `-search.minStalenessInterval=5m` cmd-line flag (`5m` is
the static interval used by Prometheus).
1. If you observe recently written data is not immediately visible/queryable, then read more about
[query latency](https://docs.victoriametrics.com/keyConcepts.html#query-latency) behavior.
1. Try upgrading to the [latest available version of VictoriaMetrics](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest)
and verifying whether the issue is fixed there.