From 0e6731323acee19195149bd77ed573d843c8e2fd Mon Sep 17 00:00:00 2001 From: hagen1778 Date: Mon, 25 Nov 2024 12:27:26 +0100 Subject: [PATCH] docs: update link for `tsdb stats` word The link was pointing to itself, which doesn't make sense. Changed it to point to https://docs.victoriametrics.com/url-examples/#apiv1statustsdb Signed-off-by: hagen1778 --- docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.md b/docs/README.md index 35f00425e4..17b02fc137 100644 --- a/docs/README.md +++ b/docs/README.md @@ -2284,7 +2284,7 @@ VictoriaMetrics returns TSDB stats at `/api/v1/status/tsdb` page in the way simi * `extra_label=LABEL=VALUE`. See [these docs](#prometheus-querying-api-enhancements) for more details. In [cluster version of VictoriaMetrics](https://docs.victoriametrics.com/cluster-victoriametrics/) each vmstorage tracks the stored time series individually. -vmselect requests stats via [/api/v1/status/tsdb](#tsdb-stats) API from each vmstorage node and merges the results by summing per-series stats. +vmselect requests stats via [/api/v1/status/tsdb](https://docs.victoriametrics.com/url-examples/#apiv1statustsdb) API from each vmstorage node and merges the results by summing per-series stats. This may lead to inflated values when samples for the same time series are spread across multiple vmstorage nodes due to [replication](#replication) or [rerouting](https://docs.victoriametrics.com/cluster-victoriametrics/?highlight=re-routes#cluster-availability).