From aa5a2616baa835a6948b2c14e195f54ce0bdc588 Mon Sep 17 00:00:00 2001
From: earthgecko <96679+earthgecko@users.noreply.github.com>
Date: Fri, 16 Aug 2024 11:29:05 +0100
Subject: [PATCH] Update rewrite-rules.conf.example - explicitly state
 aggregator

Explicitly state and relate rewrite-rules.conf to carbon-aggregator so that this info is available to the user in-situ in the example. There is ambiguity in the phrase "as soon as they are received" this can confusing because carbon-relay could be seen as where they are being received.

Related to https://github.com/graphite-project/graphite-web/pull/2845 which tries to make it clearer in the docs as well.
---
 conf/rewrite-rules.conf.example | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/conf/rewrite-rules.conf.example b/conf/rewrite-rules.conf.example
index f7bd4d1dd..c359d9f65 100644
--- a/conf/rewrite-rules.conf.example
+++ b/conf/rewrite-rules.conf.example
@@ -1,8 +1,9 @@
-# This file defines regular expression patterns that can be used to
+# This file defines regular expression patterns that can be used by
+# carbon-aggregator (as per [aggregator] section of carbon.conf) to
 # rewrite metric names in a search & replace fashion. It consists of two
 # sections, [pre] and [post]. The rules in the pre section are applied to
-# metric names as soon as they are received. The post rules are applied
-# after aggregation has taken place.
+# metric names as soon as they are received by aggregator. The post rules
+# are applied after aggregation has taken place.
 #
 # The general form of each rule is as follows:
 #