From 02e852854a3951281ae013c513b1d2e249ddaa9d Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Mon, 10 Feb 2020 22:46:40 +0200 Subject: [PATCH] README.md: refer to the article about data deletion via relabeling --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index de85efaec7..6abb45cb37 100644 --- a/README.md +++ b/README.md @@ -551,6 +551,7 @@ 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. + 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 time series occupy disk space until the next merge operation, which can never occur.