mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-21 14:44:00 +00:00
docs/Single-server-VictoriaMetrics.md: mention that -search.maxStalenessInterval
can be useful for InfluxDB and TimescaleDB users
This commit is contained in:
parent
48320cffe0
commit
c53fd515fe
1 changed files with 4 additions and 0 deletions
|
@ -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
|
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.
|
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.
|
* 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.
|
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,
|
VictoriaMetrics accepts optional `date=YYYY-MM-DD` and `topN=42` args on this page. By default `date` equals to the current date,
|
||||||
|
|
Loading…
Reference in a new issue