From a22a2e9bf4699244ed50368b730d6cd9093cf6b6 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Thu, 16 Apr 2020 17:34:59 +0300 Subject: [PATCH] docs/Single-server-VictoriaMetrics.md: typo fix: unneded -> unneeded --- docs/Single-server-VictoriaMetrics.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 29da16b244..4310c5721a 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -616,10 +616,10 @@ The delete API is intended mainly for the following cases: It isn't recommended using delete API for the following cases, since it brings non-zero overhead: -* Regular cleanups for unneded data. Just prevent writing unneeded data into VictoriaMetrics. +* Regular cleanups for unneeded data. Just prevent writing unneeded data into VictoriaMetrics. This can be done with relabeling in [vmagent](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmagent/README.md). See [this article](https://www.robustperception.io/relabelling-can-discard-targets-timeseries-and-alerts) for details. -* Reducing disk space usage by deleting unneded time series. This doesn't work as expected, since the deleted +* Reducing disk space usage by deleting unneeded time series. This doesn't work as expected, since the deleted time series occupy disk space until the next merge operation, which can never occur when deleting too old data. It is better using `-retentionPeriod` command-line flag for efficient pruning of old data.