From 71c3266fcae2001098cad015fff1d6f9d925a16c Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Wed, 22 Jul 2020 18:16:23 +0300 Subject: [PATCH] docs/Single-server-VictoriaMetrics.md: mention that it is recommended inspecting logs during troubleshooting --- docs/Single-server-VictoriaMetrics.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index d4a0558e74..b231fb9553 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -1013,6 +1013,8 @@ VictoriaMetrics also exposes currently running queries with their execution time * It is recommended upgrading to the latest available release from [this page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases), since the encountered issue could be already fixed there. +* It is recommended inspecting logs during troubleshooting, since they may contain useful information. + * 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. VictoriaMetrics [exposes](#monitoring) `vm_slow_*` metrics, which could be used as an indicator of low amounts of RAM.