From c4be49e21bc2b3ae32d2efd81aaca87dad50402b Mon Sep 17 00:00:00 2001 From: Roman Khavronenko Date: Fri, 9 Jun 2023 13:47:54 +0200 Subject: [PATCH] docs: mention stream aggregation as more efficient approach for aggregation (#4429) Signed-off-by: hagen1778 --- app/vmalert/README.md | 3 +++ docs/stream-aggregation.md | 2 +- docs/vmalert.md | 3 +++ 3 files changed, 7 insertions(+), 1 deletion(-) diff --git a/app/vmalert/README.md b/app/vmalert/README.md index 0d4b3c421..8c9beb020 100644 --- a/app/vmalert/README.md +++ b/app/vmalert/README.md @@ -526,6 +526,9 @@ Check how to replace it with [cluster VictoriaMetrics](#cluster-victoriametrics) #### Downsampling and aggregation via vmalert +_Please note, [stream aggregation](https://docs.victoriametrics.com/stream-aggregation.html) might be more efficient +for cases when downsampling or aggregation need to be applied **before data gets into the TSDB.**_ + `vmalert` can't modify existing data. But it can run arbitrary PromQL/MetricsQL queries via [recording rules](#recording-rules) and backfill results to the configured `-remoteWrite.url`. This ability allows to aggregate data. For example, the following rule will calculate the average value for diff --git a/docs/stream-aggregation.md b/docs/stream-aggregation.md index 79fd838e9..b277f1003 100644 --- a/docs/stream-aggregation.md +++ b/docs/stream-aggregation.md @@ -13,7 +13,7 @@ aliases: # streaming aggregation [vmagent](https://docs.victoriametrics.com/vmagent.html) and [single-node VictoriaMetrics](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html) -can aggregate incoming [samples](https://docs.victoriametrics.com/keyConcepts.html#raw-samples) in streaming mode by time and by labels. +can aggregate incoming [samples](https://docs.victoriametrics.com/keyConcepts.html#raw-samples) in streaming mode by time and by labels before data is written to remote storage. The aggregation is applied to all the metrics received via any [supported data ingestion protocol](https://docs.victoriametrics.com/#how-to-import-time-series-data) and/or scraped from [Prometheus-compatible targets](https://docs.victoriametrics.com/#how-to-scrape-prometheus-exporters-such-as-node-exporter). diff --git a/docs/vmalert.md b/docs/vmalert.md index 0e9db295b..8c2d59960 100644 --- a/docs/vmalert.md +++ b/docs/vmalert.md @@ -537,6 +537,9 @@ Check how to replace it with [cluster VictoriaMetrics](#cluster-victoriametrics) #### Downsampling and aggregation via vmalert +_Please note, [stream aggregation](https://docs.victoriametrics.com/stream-aggregation.html) might be more efficient +for cases when downsampling or aggregation need to be applied **before data gets into the TSDB.**_ + `vmalert` can't modify existing data. But it can run arbitrary PromQL/MetricsQL queries via [recording rules](#recording-rules) and backfill results to the configured `-remoteWrite.url`. This ability allows to aggregate data. For example, the following rule will calculate the average value for