GitBook: [1.6] 139 pages and 22 assets modified

Author: agup006

.gitbook/assets/azureloganalytics_small.png

@@ -118,9 +118,9 @@
   * [Amazon CloudWatch](pipeline/outputs/cloudwatch.md)
   * [Amazon Kinesis Data Firehose](pipeline/outputs/firehose.md)
   * [Amazon S3](pipeline/outputs/s3.md)
-  * [Azure](pipeline/outputs/azure.md)
+  * [Azure Log Analytics](pipeline/outputs/azure.md)
   * [Azure Blob](pipeline/outputs/azure_blob.md)
-  * [BigQuery](pipeline/outputs/bigquery.md)
+  * [Google Cloud BigQuery](pipeline/outputs/bigquery.md)
   * [Counter](pipeline/outputs/counter.md)
   * [Datadog](pipeline/outputs/datadog.md)
   * [Elasticsearch](pipeline/outputs/elasticsearch.md)

.gitbook/assets/image (1).png

@@ -34,7 +34,7 @@ The _Service_ section defines global properties of the service, the keys availab
 | HTTP\_Server | Enable built-in HTTP Server | Off |
 | HTTP\_Listen | Set listening interface for HTTP Server when it's enabled | 0.0.0.0 |
 | HTTP\_Port | Set TCP Port for the HTTP Server | 2020 |
-| Coro\_Stack\_Size | Set the coroutines stack size in bytes. The value must be greater than the page size of the running system. Don't set too small value (say 4096), or coroutine threads can overrun the stack buffer. Do not change the default value of this parameter unless you know what you are doing. | 24576 |
+| Coro\_Stack\_Size | Set the coroutines stack size in bytes. The value must be greater than the page size of the running system. Don't set too small value \(say 4096\), or coroutine threads can overrun the stack buffer. Do not change the default value of this parameter unless you know what you are doing. | 24576 |
 
 The following is an example of a _SERVICE_ section:
 

.gitbook/assets/image (2).png

@@ -8,7 +8,7 @@ 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%20%281%29%20%281%29.png)
+![](../../.gitbook/assets/logging_pipeline_buffer%20%281%29%20%281%29%20%281%29.png)
 
 {% hint style="info" %}
 Note that buffered data is not raw text, it's in Fluent Bit's internal binary representation.

.gitbook/assets/image (3).png

@@ -6,7 +6,7 @@ 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%20%281%29.png)
+![](../../.gitbook/assets/logging_pipeline_input%20%281%29%20%281%29.png)
 
 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**.
 

.gitbook/assets/image (4).png

@@ -6,7 +6,7 @@ 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.png)
+![](../../.gitbook/assets/logging_pipeline_output%20%281%29.png)
 
 When an output plugin is loaded, an internal _instance_ is created. Every instance has its own independent configuration. Configuration keys are often called **properties**.
 

.gitbook/assets/image (5).png

@@ -6,7 +6,7 @@ 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%20%281%29.png)
+![](../../.gitbook/assets/logging_pipeline_parser%20%281%29%20%281%29.png)
 
 The Parser allows you to convert from unstructured to structured data. As a demonstrative example consider the following Apache \(HTTP Server\) log entry:
 

.gitbook/assets/image (6).png

@@ -6,7 +6,7 @@ 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%20%281%29%20%281%29.png)
+![](../../.gitbook/assets/logging_pipeline_routing%20%281%29%20%281%29%20%281%29.png)
 
 There are two important concepts in Routing:
 

.gitbook/assets/image (7).png

@@ -1,4 +1,12 @@
-# Azure
+---
+description: 'Send logs, metrics to Azure Log Analytics'
+---
+
+# Azure Log Analytics
+
+ 
+
+ ![](../../.gitbook/assets/image%20%287%29.png) 
 
 Azure output plugin allows to ingest your records into [Azure Log Analytics](https://azure.microsoft.com/en-us/services/log-analytics/) service.
 

.gitbook/assets/image (8).png

@@ -1,4 +1,4 @@
-# BigQuery
+# Google Cloud BigQuery
 
 BigQuery output plugin is an _experimental_ plugin that allows you to stream records into [Google Cloud BigQuery](https://cloud.google.com/bigquery/) service. The implementation does not support the following, which would be expected in a full production version:
 

.gitbook/assets/image (9).png

@@ -1,5 +1,11 @@
+---
+description: Send logs and metrics to Amazon CloudWatch
+---
+
 # Amazon CloudWatch
 
+![](../../.gitbook/assets/image%20%282%29.png)
+
 The Amazon CloudWatch output plugin allows to ingest your records into the [CloudWatch Logs](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html) service. Support for CloudWatch Metrics is also provided via [EMF](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Embedded_Metric_Format_Specification.html).
 
 This is the documentation for the core Fluent Bit CloudWatch plugin written in C. It can replace the [aws/amazon-cloudwatch-logs-for-fluent-bit](https://github.com/aws/amazon-cloudwatch-logs-for-fluent-bit) Golang Fluent Bit plugin released last year. The Golang plugin was named `cloudwatch`; this new high performance CloudWatch plugin is called `cloudwatch_logs` to prevent conflicts/confusion. Check the amazon repo for the Golang plugin for details on the deprecation/migration plan for the original plugin.

.gitbook/assets/logging_pipeline.png renamed to .gitbook/assets/logging_pipeline (1) (1).png

@@ -1,3 +1,7 @@
+---
+description: Send logs to Datadog
+---
+
 # Datadog
 
 The Datadog output plugin allows to ingest your logs into [Datadog](https://app.datadoghq.com/signup).

.gitbook/assets/logging_pipeline_buffer (1).png renamed to .gitbook/assets/logging_pipeline_buffer (1) (1) (1).png

@@ -1,3 +1,7 @@
+---
+description: Send logs to Elasticsearch (including Amazon Elasticsearch Service)
+---
+
 # Elasticsearch
 
 The **es** output plugin, allows to ingest your records into a [Elasticsearch](http://www.elastic.co) database. The following instructions assumes that you have a fully operational Elasticsearch service running in your environment.

.gitbook/assets/logging_pipeline_input.png renamed to .gitbook/assets/logging_pipeline_input (1) (1).png

@@ -1,5 +1,11 @@
+---
+description: Send logs to Amazon Kinesis Firehose
+---
+
 # Amazon Kinesis Data Firehose
 
+![](../../.gitbook/assets/image%20%288%29.png)
+
 The Amazon Kinesis Data Firehose output plugin allows to ingest your records into the [Firehose](https://aws.amazon.com/kinesis/data-firehose/) service.
 
 This is the documentation for the core Fluent Bit Firehose plugin written in C. It can replace the [aws/amazon-kinesis-firehose-for-fluent-bit](https://github.com/aws/amazon-kinesis-firehose-for-fluent-bit) Golang Fluent Bit plugin released last year. The Golang plugin was named `firehose`; this new high performance and highly efficient firehose plugin is called `kinesis_firehose` to prevent conflicts/confusion.

.gitbook/assets/logging_pipeline_output.png renamed to .gitbook/assets/logging_pipeline_output (1) (1).png

@@ -1,6 +1,12 @@
+---
+description: 'Send logs, data, metrics to Amazon S3'
+---
+
 # Amazon S3
 
-The Amazon S3 output plugin allows to ingest your records into the [S3](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html) cloud object store.
+![](../../.gitbook/assets/image%20%286%29.png)
+
+The Amazon S3 output plugin allows you to ingest your records into the [S3](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html) cloud object store.
 
 The plugin can upload data to S3 using the [multipart upload API](https://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html) or using S3 [PutObject](https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutObject.html). Multipart is the default and is recommended; Fluent Bit will stream data in a series of 'parts'. This limits the amount of data it has to buffer on disk at any point in time. By default, every time 5 MiB of data have been received, a new 'part' will be uploaded. The plugin can create files up to gigabytes in size from many small chunks/parts using the multipart API. All aspects of the upload process are configurable using the configuration options.
 

.gitbook/assets/logging_pipeline_parser (1).png renamed to .gitbook/assets/logging_pipeline_parser (1) (1) (1).png

@@ -1,3 +1,7 @@
+---
+description: Send logs to Splunk HTTP Event Collector
+---
+
 # Splunk
 
 Splunk output plugin allows to ingest your records into a [Splunk Enterprise](https://www.splunk.com/en_us/products/splunk-enterprise.html) service through the HTTP Event Collector \(HEC\) interface.