From 5f9c23226adfee844443ee4d95bee79108fc18f0 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Fri, 24 Apr 2020 16:22:50 +0300 Subject: [PATCH] docs/Single-server-VictoriaMetrics.md: mention that `-search.maxStalenessInterval` can be useful for InfluxDB and TimescaleDB users --- README.md | 4 ++++ docs/Single-server-VictoriaMetrics.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/README.md b/README.md index ef5ebe021..bedcb4456 100644 --- a/README.md +++ b/README.md @@ -927,6 +927,10 @@ The most interesting metrics are: If the gaps are related to irregular intervals between samples, then try adjusting `-search.minStalenessInterval` command-line flag to value close to the maximum interval between samples. +* If you are switching from InfluxDB or TimescaleDB, then take a look at `-search.maxStalenessInterval` command-line flag. + It may be needed in order to suppress default gap filling algorithm used by VictoriaMetrics - by default it assumes + each time series is continuous instead of discrete, so it fills gaps between real samples with regular intervals. + * Metrics and labels leading to high cardinality or high churn rate can be determined at `/api/v1/status/tsdb` page. See [these docs](https://prometheus.io/docs/prometheus/latest/querying/api/#tsdb-stats) for details. VictoriaMetrics accepts optional `date=YYYY-MM-DD` and `topN=42` args on this page. By default `date` equals to the current date, diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index ef5ebe021..bedcb4456 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -927,6 +927,10 @@ The most interesting metrics are: If the gaps are related to irregular intervals between samples, then try adjusting `-search.minStalenessInterval` command-line flag to value close to the maximum interval between samples. +* If you are switching from InfluxDB or TimescaleDB, then take a look at `-search.maxStalenessInterval` command-line flag. + It may be needed in order to suppress default gap filling algorithm used by VictoriaMetrics - by default it assumes + each time series is continuous instead of discrete, so it fills gaps between real samples with regular intervals. + * Metrics and labels leading to high cardinality or high churn rate can be determined at `/api/v1/status/tsdb` page. See [these docs](https://prometheus.io/docs/prometheus/latest/querying/api/#tsdb-stats) for details. VictoriaMetrics accepts optional `date=YYYY-MM-DD` and `topN=42` args on this page. By default `date` equals to the current date,