From f7f684fa0d908e7906a70e4f642f05ef9a9bd2fb Mon Sep 17 00:00:00 2001 From: hagen1778 Date: Fri, 12 Jul 2024 11:14:27 +0200 Subject: [PATCH] docs: mention stream aggregation in churn rate section Signed-off-by: hagen1778 (cherry picked from commit fbdaba4f8c013787b656867e6bb3f33ae3b45157) --- docs/FAQ.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/FAQ.md b/docs/FAQ.md index 8c00603a3f..89482f509c 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -338,7 +338,8 @@ The main reason for high churn rate is a metric label with frequently changed va * A `hash` or `uuid` label, which changes frequently. The solution against high churn rate is to identify and eliminate labels with frequently changed values. -[Cardinality explorer](https://docs.victoriametrics.com/#cardinality-explorer) can help determining these labels. +[Cardinality explorer](https://docs.victoriametrics.com/#cardinality-explorer) can help determining these labels. If labels can't be removed, try pre-aggregating data +before it gets ingested into database with [stream aggregation](https://docs.victoriametrics.com/stream-aggregation/). The official Grafana dashboards for VictoriaMetrics contain graphs for churn rate - see [these docs](https://docs.victoriametrics.com/#monitoring) for details.