From 9873001539e26b5ba2cf629615ff65f600d9e2a0 Mon Sep 17 00:00:00 2001 From: Roman Khavronenko Date: Tue, 14 Jun 2022 09:10:44 +0200 Subject: [PATCH] docs: migrating from influx (#2720) Mention `-search.maxStalenessInterval` flag and its effect on query engine. Signed-off-by: hagen1778 --- docs/guides/migrate-from-influx.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/guides/migrate-from-influx.md b/docs/guides/migrate-from-influx.md index 6bc3efa3b0..42105509f9 100644 --- a/docs/guides/migrate-from-influx.md +++ b/docs/guides/migrate-from-influx.md @@ -196,11 +196,16 @@ Grafana will have the following form: {% include img.html href="migrate-from-influx-data-sample-in-vm.png" %} -It is noticeable that visualizations from both databases are a bit different - VictoriaMetrics shows some extra points +Visualizations from both databases are a bit different - VictoriaMetrics shows some extra points filling the gaps in the graph. This behavior is described in more detail [here](https://docs.victoriametrics.com/keyConcepts.html#range-query). In InfluxDB, we can achieve a similar behavior by adding `fill(previous)` to the query. +VictoriaMetrics fills the gaps on the graph assuming time series are always continious and not discrete. +To limit the interval on which VictoriaMetrics will try to fill the gaps try setting `-search.maxStalenessInterval` +command-line flag to the value equal to actual resolution between data points (for example, to `1ms`). + + ### Advanced usage The good thing is that knowing the basics and some aggregation functions is often enough for using MetricsQL or PromQL.