ClusterCockpit/cc-metric-collector
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-metric-collector.git synced 2024-12-24 14:49:05 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update configuration.md

Browse Source 
Add an additional receiver to have better alignment of components
This commit is contained in:
Thomas Gruber 2022-03-04 18:33:57 +01:00 committed by GitHub
parent 1961edc659
commit 8c668fcc6f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/configuration.md
View File

@ -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).
All types and possible receiver-specific configuration options can be found [here](../receivers/README.md).