From 0237d987c06fb3f7dac855f8063fd1b4a8d90121 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin <valyala@victoriametrics.com> Date: Fri, 15 Jul 2022 11:54:51 +0300 Subject: [PATCH] docs/Troubleshooting.md: mention about `-search.setLookbackToStep` command-line flag in the section explaining why `/api/v1/query_range` returns calculated data --- docs/Troubleshooting.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/Troubleshooting.md b/docs/Troubleshooting.md index e8e907db5..bcc5cfaed 100644 --- a/docs/Troubleshooting.md +++ b/docs/Troubleshooting.md @@ -50,6 +50,9 @@ If you see unexpected or unreliable query results from VictoriaMetrics, then try instead of raw samples stored in VictoriaMetrics. See [these docs](https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness) for details. + If you migrate from InfluxDB, then pass `-search.setLookbackToStep` command-line flag to single-node VictoriaMetrics + or to `vmselect` in VictoriaMetrics cluster. See also [how to migrate from InfluxDB to VictoriaMetrics](https://docs.victoriametrics.com/guides/migrate-from-influx.html). + 3. Sometimes response caching may lead to unexpected results when samples with older timestamps are ingested into VictoriaMetrics (aka [backfilling](https://docs.victoriametrics.com/#backfilling)). Try disabling response cache and see whether this helps. This can be done in the following ways: