From cbba78e091d7cad930fb8942088a9b27ac898d3e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=8C=A0=E5=BF=83=E9=9B=B6=E5=BA=A6?= <97019752@qq.com> Date: Wed, 16 Feb 2022 14:32:57 +0800 Subject: [PATCH] Correct URL:How to delete time series (#2201) Co-authored-by: lirenzuo --- docs/README.md | 2 +- docs/Single-server-VictoriaMetrics.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/README.md b/docs/README.md index 4473fba26..c3a9ca0ca 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1460,7 +1460,7 @@ cache when samples with timestamps older than `now - search.cacheTimestampOffset VictoriaMetrics doesn't support updating already existing sample values to new ones. It stores all the ingested data points for the same time series with identical timestamps. While it is possible substituting old time series with new time series via -[removal of old time series](#how-to-delete-timeseries) and then [writing new time series](#backfilling), this approach +[removal of old time series](#how-to-delete-time-series) and then [writing new time series](#backfilling), this approach should be used only for one-off updates. It shouldn't be used for frequent updates because of non-zero overhead related to data removal. diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index d98725443..f2056ed13 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -1464,7 +1464,7 @@ cache when samples with timestamps older than `now - search.cacheTimestampOffset VictoriaMetrics doesn't support updating already existing sample values to new ones. It stores all the ingested data points for the same time series with identical timestamps. While it is possible substituting old time series with new time series via -[removal of old time series](#how-to-delete-timeseries) and then [writing new time series](#backfilling), this approach +[removal of old time series](#how-to-delete-time-series) and then [writing new time series](#backfilling), this approach should be used only for one-off updates. It shouldn't be used for frequent updates because of non-zero overhead related to data removal.