mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2025-01-20 07:19:17 +01:00
update wiki pages
parent
6fa48e81b6
commit
a1c3ed0ccf
@ -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)
|
instead of raw samples stored in VictoriaMetrics. See [these docs](https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness)
|
||||||
for details.
|
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
|
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)).
|
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:
|
Try disabling response cache and see whether this helps. This can be done in the following ways:
|
||||||
|
Loading…
Reference in New Issue
Block a user