Merge branch 'master' into lynettemiles/sc-136235/update-fluent-bit-docs-pipeline-outputs-datadog

Signed-off-by: Lynette  Miles <[email protected]>

Author: esmerel

pipeline/outputs/counter.md

@@ -1,24 +1,24 @@
 # Counter
 
-_Counter_ is a very simple plugin that counts how many records it's getting upon flush time. Plugin output is as follows:
+_Counter_ is a plugin that counts how many records it's getting upon flush time. Plugin output is as follows:
 
 ```text
 [TIMESTAMP, NUMBER_OF_RECORDS_NOW] (total = RECORDS_SINCE_IT_STARTED)
 ```
 
-## Getting Started
+## Get started
 
-You can run the plugin from the command line or through the configuration file:
+You can run the plugin from the command line or through the configuration file.
 
-### Command Line
+### Command line
 
-From the command line you can let Fluent Bit count up a data with the following options:
+From the command line you can let Fluent Bit count data with the following options:
 
 ```shell
 fluent-bit -i cpu -o counter
 ```
 
-### Configuration File
+### Configuration file
 
 In your main configuration file append the following:
 
@@ -30,7 +30,7 @@ pipeline:
   inputs:
     - name: cpu
       tag: cpu
-      
+
   outputs:
     - name: counter
       match: '*'
@@ -54,13 +54,13 @@ pipeline:
 
 ## Testing
 
-Once Fluent Bit is running, you will see the reports in the output interface similar to this:
+When Fluent Bit is running, you will see the reports similar to this in the output interface:
 
-```shell
+```text
 ...
 1500484743,1 (total = 1)
 1500484744,1 (total = 2)
 1500484745,1 (total = 3)
 1500484746,1 (total = 4)
 1500484747,1 (total = 5)
-```
+```

pipeline/outputs/dash0.md

@@ -22,7 +22,7 @@ Stream logs to [Dash0](https://www.dash0.com) by utilizing the [OpenTelemetry pl
 The OpenTelemetry output plugin supports TLS/SSL.
 For more details about the properties available and general configuration, see [TLS/SSL](../../administration/transport-security.md).
 
-## Getting started
+## Get started
 
 To get started with sending logs to Dash0:
 
@@ -34,9 +34,9 @@ To get started with sending logs to Dash0:
 
 ```yaml
 pipeline:
-    
+
   outputs:
-    - name: opentelemetry      
+    - name: opentelemetry
       match: '*'
       host: ingress.eu-west-1.aws.dash0.com
       port: 443
@@ -45,6 +45,7 @@ pipeline:
       logs_uri: /v1/logs
       traces_uri: /v1/traces
 ```
+
 {% endtab %}
 {% tab title="fluent-bit.conf" %}
 
@@ -65,4 +66,4 @@ pipeline:
 
 ## References
 
-- [Dash0 documentation](https://www.dash0.com/documentation/dash0)
+- [Dash0 documentation](https://www.dash0.com/documentation/dash0)

pipeline/outputs/dynatrace.md

@@ -4,9 +4,7 @@ description: Send logs to Dynatrace
 
 # Dynatrace
 
-Stream logs to [Dynatrace](https://www.dynatrace.com) by utilizing the **http**
-plugin to send data to the
-[Dynatrace generic log ingest API](https://docs.dynatrace.com/docs/shortlink/lma-generic-log-ingestion).
+Stream logs to [Dynatrace](https://www.dynatrace.com) by utilizing the `http` plugin to send data to the [Dynatrace generic log ingest API](https://docs.dynatrace.com/docs/shortlink/lma-generic-log-ingestion).
 
 ## Configuration parameters
 
@@ -20,26 +18,24 @@ plugin to send data to the
 | `uri`                      | Specify the HTTP URI for Dynatrace log ingest API. | `/api/v2/logs/ingest` |
 | `format`                   | The data format to be used in the HTTP request body. | `json` |
 | `json_date_format`         | Date format standard for JSON. | `iso8601` |
-| `json_date_key`            | Fieldname specifying message timestamp. | `timestamp` |
+| `json_date_key`            | Field name specifying message timestamp. | `timestamp` |
 | `tls`                      | Specify to use TLS. | `on` |
 | `tls.verify`               | TLS verification. | `on` |
 
-## Getting started
+## Get started
 
 To get started with sending logs to Dynatrace:
 
-1. Get a [Dynatrace API](https://docs.dynatrace.com/docs/shortlink/api-authentication)
-   token with the `logs.ingest` (Ingest Logs) scope.
-1. Determine your Dynatrace
-   [environment ID](https://docs.dynatrace.com/docs/shortlink/monitoring-environment#environment-id).
-   1. In your main Fluent Bit configuration file, append the following `Output` section:
+1. Get a [Dynatrace API](https://docs.dynatrace.com/docs/shortlink/api-authentication) token with the `logs.ingest` (Ingest Logs) scope.
+1. Determine your Dynatrace [environment ID](https://docs.dynatrace.com/docs/shortlink/monitoring-environment#environment-id).
+1. In your main Fluent Bit configuration file, append the following `Output` section:
 
 {% tabs %}
 {% tab title="fluent-bit.yaml" %}
 
    ```yaml
    pipeline:
-          
+
      outputs:
        - name: http
          match: '*'
@@ -54,12 +50,12 @@ To get started with sending logs to Dynatrace:
          json_date_format: iso8601
          json_date_key: timestamp
          tls: on
-         tls.verify: on      
+         tls.verify: on
    ```
-   
+
 {% endtab %}
 {% tab title="fluent-bit.conf" %}
-   
+
    ```text
    [OUTPUT]
      name         http
@@ -76,13 +72,14 @@ To get started with sending logs to Dynatrace:
      tls          On
      tls.verify   On
    ```
-   
+
 {% endtab %}
 {% endtabs %}
 
 ## References
 
 - [Dynatrace Fluent Bit documentation](https://docs.dynatrace.com/docs/shortlink/lma-stream-logs-with-fluent-bit)
-- [Fluent Bit integration in Dynatrace Hub](https://www.dynatrace.com/hub/detail/fluent-bit/?filter=log-management-and-analytics) 
+- [Fluent Bit integration in Dynatrace Hub](https://www.dynatrace.com/hub/detail/fluent-bit/?filter=log-management-and-analytics)
 - [Video: Stream a Log File to Dynatrace using Fluent Bit](https://www.youtube.com/watch?v=JJJNxhtJ6R0)
-- [Blog: Easily stream logs from Fluent Bit to Dynatrace](https://www.dynatrace.com/news/blog/easily-stream-logs-with-fluent-bit-to-dynatrace/)
+- [Blog: Easily stream logs from Fluent Bit to
+  Dynatrace](https://www.dynatrace.com/news/blog/easily-stream-logs-with-fluent-bit-to-dynatrace/)