README.md: refer to the article about data deletion via relabeling

This commit is contained in:
Aliaksandr Valialkin 2020-02-10 22:46:40 +02:00
parent 9e6e2319b9
commit 02e852854a

View File

@ -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: 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 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 - 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. time series occupy disk space until the next merge operation, which can never occur.