mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-15 00:13:30 +01:00
docs: mention stream aggregation as more efficient approach for aggregation (#4429)
Signed-off-by: hagen1778 <roman@victoriametrics.com>
This commit is contained in:
parent
5518cb2f9a
commit
91612b38cd
@ -526,6 +526,9 @@ Check how to replace it with [cluster VictoriaMetrics](#cluster-victoriametrics)
|
|||||||
|
|
||||||
#### Downsampling and aggregation via vmalert
|
#### 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
|
`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`.
|
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
|
This ability allows to aggregate data. For example, the following rule will calculate the average value for
|
||||||
|
@ -13,7 +13,7 @@ aliases:
|
|||||||
# streaming aggregation
|
# streaming aggregation
|
||||||
|
|
||||||
[vmagent](https://docs.victoriametrics.com/vmagent.html) and [single-node VictoriaMetrics](https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html)
|
[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)
|
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).
|
and/or scraped from [Prometheus-compatible targets](https://docs.victoriametrics.com/#how-to-scrape-prometheus-exporters-such-as-node-exporter).
|
||||||
|
|
||||||
|
@ -537,6 +537,9 @@ Check how to replace it with [cluster VictoriaMetrics](#cluster-victoriametrics)
|
|||||||
|
|
||||||
#### Downsampling and aggregation via vmalert
|
#### 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
|
`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`.
|
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
|
This ability allows to aggregate data. For example, the following rule will calculate the average value for
|
||||||
|
Loading…
Reference in New Issue
Block a user