diagrams: put Routing in a circle

Signed-off-by: Eduardo Silva <[email protected]>

Author: edsiper

.bookignore

@@ -1,4 +1,6 @@
 *~
 *.#
 *.sh
+*.mmd
+#*
 

diagrams/logging_pipeline.png

@@ -2,7 +2,7 @@ graph LR;
     A(Input)-->B(Parser)
     B-->C(Filter)
     C-->D(Buffer)
-    D-->E(Routing)
+    D-->E((Routing))
       E-->G1(Output 1)
       E-->G2(Output 2)
       E-->G3(Output N)

diagrams/logging_pipeline_buffer.png

@@ -2,7 +2,7 @@ graph LR;
     A(Input)-->B(Parser)
     B-->C(Filter)
     C-->D(Buffer)
-    D-->E(Routing)
+    D-->E((Routing))
       E-->G1(Output 1)
       E-->G2(Output 2)
       E-->G3(Output N)

diagrams/logging_pipeline_filter.png

@@ -2,7 +2,7 @@ graph LR;
     A(Input)-->B(Parser)
     B-->C(Filter)
     C-->D(Buffer)
-    D-->E(Routing)
+    D-->E((Routing))
       E-->G1(Output 1)
       E-->G2(Output 2)
       E-->G3(Output N)

diagrams/logging_pipeline_input.png

@@ -2,7 +2,7 @@ graph LR;
     A(Input)-->B(Parser)
     B-->C(Filter)
     C-->D(Buffer)
-    D-->E(Routing)
+    D-->E((Routing))
       E-->G1(Output 1)
       E-->G2(Output 2)
       E-->G3(Output N)

diagrams/logging_pipeline_output.png

@@ -2,7 +2,7 @@ graph LR;
     A(Input)-->B(Parser)
     B-->C(Filter)
     C-->D(Buffer)
-    D-->E(Routing)
+    D-->E((Routing))
       E-->G1(Output 1)
       E-->G2(Output 2)
       E-->G3(Output N)

diagrams/logging_pipeline_parser.png

@@ -2,7 +2,7 @@ graph LR;
     A(Input)-->B(Parser)
     B-->C(Filter)
     C-->D(Buffer)
-    D-->E(Routing)
+    D-->E((Routing))
       E-->G1(Output 1)
       E-->G2(Output 2)
       E-->G3(Output N)

diagrams/logging_pipeline_routing.png

@@ -2,7 +2,7 @@ graph LR;
     A(Input)-->B(Parser)
     B-->C(Filter)
     C-->D(Buffer)
-    D-->E(Routing)
+    D-->E((Routing))
       E-->G1(Output 1)
       E-->G2(Output 2)
       E-->G3(Output N)

diagrams/src/logging_pipeline.mmd

@@ -2,7 +2,7 @@
 
 [Fluent Bit](http://fluentbit.io) is a straightforward tool and to get started with it we need to understand it basic workflow. Consider the following diagram a global overview of it:
 
-![Fluent Bit Workflow](../imgs/flb_workflow.jpg)
+![Fluent Bit Workflow](../diagrams/logging_pipeline.png)
 
 | Interface | Description |
 |-----------|-------------|

diagrams/src/logging_pipeline_buffer.mmd

@@ -2,7 +2,7 @@
 
 When the data or logs are ready to be routed to some destination, by default they are buffered in memory.
 
-![](../imgs/flb_workflow_buffer.jpg)
+![](../diagrams/logging_pipeline_buffer.png)
 
 > Note that buffered data is not longer a raw text, instead it's in Fluent Bit internal binary representation.
 

diagrams/src/logging_pipeline_filter.mmd

@@ -2,7 +2,7 @@
 
 In production environments we want to have full control of the data we are collecting, filtering is an important feature that allows to __alter__ the data before to deliver it to some destination.
 
-![](../imgs/flb_workflow_filter.jpg)
+![](../diagrams/logging_pipeline_filter.png)
 
 Filtering is implemented through plugins, so each filter available could be used to match, exclude or enrich your logs with some specific metadata.
 

diagrams/src/logging_pipeline_input.mmd

@@ -2,7 +2,7 @@
 
 [Fluent Bit](http://fluentbit.io) provides different _Input Plugins_ to gather information from different sources, some of them just collect data from log files while others can gather metrics information from the operating system. There are many plugins for different needs.
 
-![](../imgs/flb_workflow_input.jpg)
+![](../diagrams/logging_pipeline_input.png)
 
 When an input plugin is loaded, an internal _instance_ is created. Every instance have it own and independent configuration. Configuration keys are often called __properties__.
 

diagrams/src/logging_pipeline_output.mmd

@@ -2,7 +2,7 @@
 
 The output interface allows to define destinations for the data. Common destinations are remote services, local file system or standard interface within others. Otputs are implemented as plugins and there are many available.
 
-![](../imgs/flb_workflow_output.jpg)
+![](../diagrams/logging_pipeline_output.png)
 
 When an output plugin is loaded, an internal _instance_ is created. Every instance have it own and independent configuration. Configuration keys are often called __properties__.
 

diagrams/src/logging_pipeline_parser.mmd

@@ -2,7 +2,7 @@
 
 Dealing with raw strings is a constant pain; having a structure is highly desired. Ideally we want to set a structure to the incoming data by the Input Plugins as soon as they are collected:
 
-![](../imgs/flb_workflow_parser.jpg)
+![](../diagrams/logging_pipeline_parser.png)
 
 The Parser allows you to convert from unstructured to structured data. As a demonstrative example consider the following Apache (HTTP Server) log entry:
 

diagrams/src/logging_pipeline_routing.mmd

@@ -2,7 +2,7 @@
 
 Routing is a core feature that allows to __route__ your data through Filters and finally to one or multiple destinations.
 
-![](../imgs/flb_workflow_routing.jpg)
+![](../diagrams/logging_pipeline_routing.png)
 
 There are two important concepts in Routing: