GitBook: [1.6] 6 pages and one asset modified

Author: agup006

.gitbook/assets/image.png

@@ -177,6 +177,12 @@ The following configuration file example demonstrates how to collect CPU metrics
     Match my*cpu
 ```
 
+## Visualize <a id="config_include_file"></a>
+
+You can also visualize Fluent Bit INPUT, FILTER, and OUTPUT configuration via [https://config.calyptia.com](https://config.calyptia.com)
+
+![](../../.gitbook/assets/image.png)
+
 ## Include File <a id="config_include_file"></a>
 
 To avoid complicated long configuration files is better to split specific parts in different files and call them \(include\) from one main file.

administration/configuring-fluent-bit/configuration-file.md

@@ -86,3 +86,4 @@ Alpine Linux uses Musl C library instead of Glibc. Musl is not fully compatible
 Our Docker containers images are deployed thousands of times per day, we take security and stability very seriously.
 
 The _latest_ tag _most of the time_ points to the latest stable image. When we release a major update to Fluent Bit like for example from v1.3.x to v1.4.0, we don't move _latest_ tag until 2 weeks after the release. That give us extra time to verify with our community that everything works as expected.
+

installation/docker.md

@@ -128,3 +128,4 @@ To halt the Fluent Bit service, just execute the "stop" command.
 ```text
 % sc.exe stop fluent-bit
 ```
+

installation/windows.md

@@ -14,3 +14,4 @@ It's strongly recommended to always use the stable release of Fluent Bit recipe
 ## Fluent Bit and other architectures
 
 Fluent Bit >= v1.1.x fully supports x86\_64, x86, arm32v7 and arm64v8.
+

installation/yocto-embedded-linux.md

@@ -7,16 +7,16 @@ Content:
 * [Configuration Parameters](statsd.md#config)
 * [Configuration Examples](statsd.md#config_example)
 
-## Configuration Parameters {#config}
+## Configuration Parameters <a id="config"></a>
 
 The plugin supports the following configuration parameters:
 
-| Key      | Description                              | Default |
-| :------- | :--------------------------------------- | :------ |
-| Listen   | Listener network interface.              | 0.0.0.0 |
-| Port     | UDP port where listening for connections | 8125    |
+| Key | Description | Default |
+| :--- | :--- | :--- |
+| Listen | Listener network interface. | 0.0.0.0 |
+| Port | UDP port where listening for connections | 8125 |
 
-## Configuration Examples {#config_example}
+## Configuration Examples <a id="config_example"></a>
 
 Here is a configuration example.
 
@@ -40,5 +40,8 @@ echo "active:99|g"     | nc -q0 -u 127.0.0.1 8125
 
 Fluent Bit will produce the following records:
 
-    [0] statsd.0: [1574905088.971380537, {"type"=>"counter", "bucket"=>"click", "value"=>10.000000, "sample_rate"=>0.100000}]
-    [0] statsd.0: [1574905141.863344517, {"type"=>"gauge", "bucket"=>"active", "value"=>99.000000, "incremental"=>0}]
+```text
+[0] statsd.0: [1574905088.971380537, {"type"=>"counter", "bucket"=>"click", "value"=>10.000000, "sample_rate"=>0.100000}]
+[0] statsd.0: [1574905141.863344517, {"type"=>"gauge", "bucket"=>"active", "value"=>99.000000, "incremental"=>0}]
+```
+

pipeline/inputs/statsd.md

@@ -81,7 +81,7 @@ In your main configuration file append the following _Input_ & _Output_ sections
 
 ### Multi-line example
 
-When using multi-line configuration you need to first specify `Multiline On` in the configuration and use the `Parser_Firstline` and additional parser parameters `Parser_N` if needed. If we are trying to read the following Java Stacktrace as a single event 
+When using multi-line configuration you need to first specify `Multiline On` in the configuration and use the `Parser_Firstline` and additional parser parameters `Parser_N` if needed. If we are trying to read the following Java Stacktrace as a single event
 
 ```text
 Dec 14 06:41:08 Exception in thread "main" java.lang.RuntimeException: Something has gone wrong, aborting!
@@ -92,7 +92,7 @@ Dec 14 06:41:08 Exception in thread "main" java.lang.RuntimeException: Something
     at com.myproject.module.MyProject.main(MyProject.java:6)
 ```
 
-We need to specify a `Parser_Firstline` parameter that matches the first line of a multi-line event. Once a match is made Fluent Bit will read all future lines until another match with `Parser_Firstline` is made . 
+We need to specify a `Parser_Firstline` parameter that matches the first line of a multi-line event. Once a match is made Fluent Bit will read all future lines until another match with `Parser_Firstline` is made .
 
 In the case above we can use the following parser, that extracts the Time as `time` and the remaining portion of the multiline as `log`
 
@@ -115,7 +115,7 @@ If we want to further parse the entire event we can add additional parsers with
     Regex /(?<time>Dec \d+ \d+\:\d+\:\d+)(?<message>.*)/
     Time_Key  time
     Time_Format %b %d %H:%M:%S
-    
+
 [INPUT]
     Name             tail
     Multiline        On
@@ -127,14 +127,14 @@ If we want to further parse the entire event we can add additional parsers with
     Match            *
 ```
 
-Our output will be as follows. 
+Our output will be as follows.
 
 ```text
 [0] tail.0: [1607928428.466041977, {"message"=>"Exception in thread "main" java.lang.RuntimeException: Something has gone wrong, aborting!
-	at com.myproject.module.MyProject.badMethod(MyProject.java:22)
-	at com.myproject.module.MyProject.oneMoreMethod(MyProject.java:18)
-	at com.myproject.module.MyProject.anotherMethod(MyProject.java:14)
-	at com.myproject.module.MyProject.someMethod(MyProject.java:10)", "message"=>"at com.myproject.module.MyProject.main(MyProject.java:6)"}]
+    at com.myproject.module.MyProject.badMethod(MyProject.java:22)
+    at com.myproject.module.MyProject.oneMoreMethod(MyProject.java:18)
+    at com.myproject.module.MyProject.anotherMethod(MyProject.java:14)
+    at com.myproject.module.MyProject.someMethod(MyProject.java:10)", "message"=>"at com.myproject.module.MyProject.main(MyProject.java:6)"}]
 ```
 
 ## Tailing files keeping state <a id="keep_state"></a>