From 18f8e90bd8129410e050c5cab82cef7e50114ba2 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Thu, 17 Aug 2023 15:24:44 +0200 Subject: [PATCH] docs/stream-aggregation.md: typo fix after 54f522ac257ea82db2ca18d0e458921f8ec5a510 --- docs/stream-aggregation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/stream-aggregation.md b/docs/stream-aggregation.md index 6882cb401..5970c5ce2 100644 --- a/docs/stream-aggregation.md +++ b/docs/stream-aggregation.md @@ -687,7 +687,7 @@ If you use [vmagent in cluster mode](https://docs.victoriametrics.com/vmagent.ht then be careful when aggregating metrics via `by`, `without` or modifying via `*_relabel_configs` parameters, since incorrect usage may result in duplicates and data collision. For example, if more than one `vmagent` instance calculates `increase` for metric `http_requests_total` with `by: [path]` directive, then all the `vmagent` instances will aggregate samples to the same set of time series with different `path` labels. -The proper fix would be to add an unique [`-remoteWrite.label`]https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics() per each `vmagent`, +The proper fix would be to add an unique [`-remoteWrite.label`](https://docs.victoriametrics.com/vmagent.html#adding-labels-to-metrics) per each `vmagent`, so every `vmagent` aggregates data into distinct set of time series. These time series then can be aggregated later as needed during querying. For example, if `vmagent` instances run in Docker or Kubernetes, then you can refer `POD_NAME` or `HOSTNAME` environment variables