Merge pull request #1394 from fluent/alexakreizinger/sc-94919/replace-input-image-with-mermaid-chart

Replace "Concepts" images with Mermaid charts

Author: alexakreizinger

concepts/data-pipeline/buffer.md

@@ -8,7 +8,19 @@ Previously defined in the [Buffering](../buffering.md) concept section, the `buf
 
 The `buffer` phase already contains the data in an immutable state, meaning, no other filter can be applied.
 
-![](<../../.gitbook/assets/logging\_pipeline\_buffer (1) (1) (2) (2) (2) (2) (2) (2) (2) (1).png>)
+```mermaid
+graph LR
+    accTitle: Fluent Bit data pipeline
+    accDescr: The Fluent Bit data pipeline includes input, a parser, a filter, a buffer, routing, and various outputs.
+    A[Input] --> B[Parser]
+    B --> C[Filter]
+    C --> D[Buffer]
+    D --> E((Routing))
+    E --> F[Output 1]
+    E --> G[Output 2]
+    E --> H[Output 3]
+    style D stroke:darkred,stroke-width:2px;
+```
 
 {% hint style="info" %}
 Note that buffered data is not raw text, it's in Fluent Bit's internal binary representation.

concepts/data-pipeline/filter.md

@@ -6,7 +6,19 @@ description: Modify, Enrich or Drop your records
 
 In production environments we want to have full control of the data we are collecting, filtering is an important feature that allows us to **alter** the data before delivering it to some destination.
 
-![](<../../.gitbook/assets/logging\_pipeline\_filter (1) (2) (2) (2) (2) (2) (2) (1).png>)
+```mermaid
+graph LR
+    accTitle: Fluent Bit data pipeline
+    accDescr: The Fluent Bit data pipeline includes input, a parser, a filter, a buffer, routing, and various outputs.
+    A[Input] --> B[Parser]
+    B --> C[Filter]
+    C --> D[Buffer]
+    D --> E((Routing))
+    E --> F[Output 1]
+    E --> G[Output 2]
+    E --> H[Output 3]
+    style C stroke:darkred,stroke-width:2px;
+```
 
 Filtering is implemented through plugins, so each filter available could be used to match, exclude or enrich your logs with some specific metadata.
 

concepts/data-pipeline/input.md

@@ -6,7 +6,19 @@ description: The way to gather data from your sources
 
 [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.
 
-![](<../../.gitbook/assets/logging\_pipeline\_input (1) (2) (2) (2) (2) (2) (2) (2) (1).png>)
+```mermaid
+graph LR
+    accTitle: Fluent Bit data pipeline
+    accDescr: The Fluent Bit data pipeline includes input, a parser, a filter, a buffer, routing, and various outputs.
+    A[Input] --> B[Parser]
+    B --> C[Filter]
+    C --> D[Buffer]
+    D --> E((Routing))
+    E --> F[Output 1]
+    E --> G[Output 2]
+    E --> H[Output 3]
+    style A stroke:darkred,stroke-width:2px;
+```
 
 When an input plugin is loaded, an internal _instance_ is created. Every instance has its own and independent configuration. Configuration keys are often called **properties**.
 

concepts/data-pipeline/output.md

@@ -6,7 +6,21 @@ description: 'Destinations for your data: databases, cloud services and more!'
 
 The output interface allows us to define destinations for the data. Common destinations are remote services, local file system or standard interface with others. Outputs are implemented as plugins and there are many available.
 
-![](<../../.gitbook/assets/logging\_pipeline\_output (1) (1).png>)
+```mermaid
+graph LR
+    accTitle: Fluent Bit data pipeline
+    accDescr: The Fluent Bit data pipeline includes input, a parser, a filter, a buffer, routing, and various outputs.
+    A[Input] --> B[Parser]
+    B --> C[Filter]
+    C --> D[Buffer]
+    D --> E((Routing))
+    E --> F[Output 1]
+    E --> G[Output 2]
+    E --> H[Output 3]
+    style F stroke:darkred,stroke-width:2px;
+    style G stroke:darkred,stroke-width:2px;
+    style H stroke:darkred,stroke-width:2px;
+```
 
 When an output plugin is loaded, an internal _instance_ is created. Every instance has its own independent configuration. Configuration keys are often called **properties**.
 

concepts/data-pipeline/parser.md

@@ -6,8 +6,19 @@ description: Convert Unstructured to Structured messages
 
 Dealing with raw strings or unstructured messages 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:
 
-![](<../../.gitbook/assets/logging\_pipeline\_parser (1) (1) (1) (1) (2) (2) (2) (3) (3) (3) (3) (3) (1).png>)
-
+```mermaid
+graph LR
+    accTitle: Fluent Bit data pipeline
+    accDescr: The Fluent Bit data pipeline includes input, a parser, a filter, a buffer, routing, and various outputs.
+    A[Input] --> B[Parser]
+    B --> C[Filter]
+    C --> D[Buffer]
+    D --> E((Routing))
+    E --> F[Output 1]
+    E --> G[Output 2]
+    E --> H[Output 3]
+    style B stroke:darkred,stroke-width:2px;
+```
 The Parser allows you to convert from unstructured to structured data. As a demonstrative example consider the following Apache (HTTP Server) log entry:
 
 ```

concepts/data-pipeline/router.md

@@ -6,7 +6,19 @@ description: Create flexible routing rules
 
 Routing is a core feature that allows to **route** your data through Filters and finally to one or multiple destinations. The router relies on the concept of [Tags](../key-concepts.md) and [Matching](../key-concepts.md) rules
 
-![](<../../.gitbook/assets/logging\_pipeline\_routing (1) (1) (2) (2) (2) (2) (2) (2) (2) (1) (1).png>)
+```mermaid
+graph LR
+    accTitle: Fluent Bit data pipeline
+    accDescr: The Fluent Bit data pipeline includes input, a parser, a filter, a buffer, routing, and various outputs.
+    A[Input] --> B[Parser]
+    B --> C[Filter]
+    C --> D[Buffer]
+    D --> E((Routing))
+    E --> F[Output 1]
+    E --> G[Output 2]
+    E --> H[Output 3]
+    style E stroke:darkred,stroke-width:2px;
+```
 
 There are two important concepts in Routing:
 
@@ -77,7 +89,7 @@ The following example demonstrates how to route data from sources based on a reg
 
 [OUTPUT]
     Name         stdout
-    Match_regex  .*_sensor_[AB] 
+    Match_regex  .*_sensor_[AB]
 ```
 
 In this configuration, the **Match_regex** rule is set to `.*_sensor_[AB]`. This regular expression will match any Tag that ends with "_sensor_A" or "_sensor_B", regardless of what precedes it.