From 8c668fcc6fda92b116783588c559646b6268adcf Mon Sep 17 00:00:00 2001
From: Thomas Gruber <Thomas.Roehl@googlemail.com>
Date: Fri, 4 Mar 2022 18:33:57 +0100
Subject: [PATCH] Update configuration.md

Add an additional receiver to have better alignment of components
---
 docs/configuration.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/configuration.md b/docs/configuration.md
index 75c7aa5..a13d3a5 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -37,11 +37,12 @@ flowchart LR
   subgraph Receivers ["Receivers"]
   direction TB
   nats["NATS"]
+  httprecv["HTTP"]
   miscrecv[...]
   end
 
   subgraph calc["Aggregator"]
-  direction TB
+  direction LR
   cache["Cache"]
   agg["Calculator"]
   end
@@ -60,6 +61,7 @@ flowchart LR
   misc --> CollectorManager
 
   nats  --> ReceiverManager["ReceiverManager"]
+  httprecv --> ReceiverManager
   miscrecv --> ReceiverManager
 
   CollectorManager --> newrouter["Router"]
@@ -184,4 +186,4 @@ The receivers are a special feature of the CC Metric Collector to enable simpler
 
 This example configuration creates two receivers with the names `nats_rack0` and `nats_rack1`. While one subscribes to metrics published with the `rack0` subject, the other one subscribes to the `rack0` subject. The NATS server is the same as it manages all subjects in a subnet. (As example, the router could add tags `rack=0` and `rack=1` respectively to the received metrics.)
 
-All types and possible receiver-specific configuration options can be found [here](../receivers/README.md).
\ No newline at end of file
+All types and possible receiver-specific configuration options can be found [here](../receivers/README.md).