VictoriaMetrics/docs/stream-aggregation
2024-08-10 08:12:38 +03:00
..
configuration docs: stream aggregation updated structure, added common mistakes section 2024-08-10 08:12:38 +03:00
_index.md docs: stream aggregation updated structure, added common mistakes section 2024-08-10 08:12:38 +03:00
common-mistakes.md docs: stream aggregation updated structure, added common mistakes section 2024-08-10 08:12:38 +03:00
key-concepts.md docs: stream aggregation updated structure, added common mistakes section 2024-08-10 08:12:38 +03:00
README.md docs: stream aggregation updated structure, added common mistakes section 2024-08-10 08:12:38 +03:00
troubleshooting.md docs: stream aggregation updated structure, added common mistakes section 2024-08-10 08:12:38 +03:00
use-cases.md docs: stream aggregation updated structure, added common mistakes section 2024-08-10 08:12:38 +03:00

vmagent and single-node VictoriaMetrics can aggregate incoming samples in streaming mode by time and by labels before data is written to remote storage (or local storage for single-node VictoriaMetrics). The aggregation is applied to all the metrics received via any supported data ingestion protocol and/or scraped from Prometheus-compatible targets after applying all the configured relabeling stages.

By default, stream aggregation ignores timestamps associated with the input samples. It expects that the ingested samples have timestamps close to the current time. See how to ignore old samples.

Next steps

{{% section %}}