From 6c68b8aa8132c05aa13b42748005a54dbb8f1602 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Mon, 4 May 2020 00:41:47 +0300 Subject: [PATCH] docs/Single-server-VictoriaMetrics.md: mention that it is recommended upgrading to the latest release before reporting issues --- README.md | 4 ++++ docs/Single-server-VictoriaMetrics.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/README.md b/README.md index 9a69999b5..1109fabec 100644 --- a/README.md +++ b/README.md @@ -907,11 +907,15 @@ The most interesting metrics are: * `vm_free_disk_space_bytes` - free space left at `-storageDataPath`. * `sum(vm_data_size_bytes)` - the total data size on disk. + ### Troubleshooting * It is recommended to use default command-line flag values (i.e. don't set them explicitly) until the need of tweaking these flag values arises. +* It is recommended upgrading to the latest available release from [this page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases), + since the issue could be already fixed there. + * If VictoriaMetrics works slowly and eats more than a CPU core per 100K ingested data points per second, then it is likely you have too many active time series for the current amount of RAM. It is recommended increasing the amount of RAM on the node with VictoriaMetrics in order to improve diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 9a69999b5..1109fabec 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -907,11 +907,15 @@ The most interesting metrics are: * `vm_free_disk_space_bytes` - free space left at `-storageDataPath`. * `sum(vm_data_size_bytes)` - the total data size on disk. + ### Troubleshooting * It is recommended to use default command-line flag values (i.e. don't set them explicitly) until the need of tweaking these flag values arises. +* It is recommended upgrading to the latest available release from [this page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases), + since the issue could be already fixed there. + * If VictoriaMetrics works slowly and eats more than a CPU core per 100K ingested data points per second, then it is likely you have too many active time series for the current amount of RAM. It is recommended increasing the amount of RAM on the node with VictoriaMetrics in order to improve