mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-15 08:23:34 +01:00
docs: migrating from influx (#2720)
Mention `-search.maxStalenessInterval` flag and its effect on query engine. Signed-off-by: hagen1778 <roman@victoriametrics.com>
This commit is contained in:
parent
b48ca34e05
commit
9873001539
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user