From 62e8854c570d2c00ba25eda3173bd6fc611bb8bd Mon Sep 17 00:00:00 2001
From: Alexander Rovner <124143655+arov00@users.noreply.github.com>
Date: Tue, 20 Feb 2024 14:32:12 +0100
Subject: [PATCH] Update 02_kafka_setup.adoc

---
 docs/installation/src/02_kafka_setup.adoc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/installation/src/02_kafka_setup.adoc b/docs/installation/src/02_kafka_setup.adoc
index 7c25cef..57804db 100644
--- a/docs/installation/src/02_kafka_setup.adoc
+++ b/docs/installation/src/02_kafka_setup.adoc
@@ -41,4 +41,6 @@ This is the exact same thing as _aggregated_ except there are no hashmap and oth
 
 ===== Metrics raw telegraf
 You can have multiple raw topics. For example one per environment or one per kafka cluster. The topic name is up to you, just don't forget to configure it properly when you deploy telegraf (see Kubernetes section).
-
+Give some special consideration to the `retention.ms` setting for the raw metrics topics. For example, if you want to distribute the cost of your monthly bill based on the raw metrics scraped over the course of the
+month then it is a good idea to retain the scraped data for more than 30 days. This gives people time to ask questions about their bill and also gives the opportunity to reprocess the metrics with new pricing rules/contexts
+if needed.