Data pipeline: update titles to sentence case + unwrap lines

Signed-off-by: Alexa Kreizinger <[email protected]>
Signed-off-by: Tom <[email protected]>

Author: alexakreizinger

SUMMARY.md

@@ -90,95 +90,96 @@
 
 ## Data pipeline
 
-* [Pipeline Monitoring](pipeline/pipeline-monitoring.md)
+* [Pipeline monitoring](pipeline/pipeline-monitoring.md)
 * [Inputs](pipeline/inputs/README.md)
   * [Collectd](pipeline/inputs/collectd.md)
-  * [CPU Log Based Metrics](pipeline/inputs/cpu-metrics.md)
-  * [Disk I/O Log Based Metrics](pipeline/inputs/disk-io-metrics.md)
-  * [Docker Events](pipeline/inputs/docker-events.md)
-  * [Docker Log Based Metrics](pipeline/inputs/docker-metrics.md)
+  * [CPU metrics](pipeline/inputs/cpu-metrics.md)
+  * [Disk I/O metrics](pipeline/inputs/disk-io-metrics.md)
+  * [Docker events](pipeline/inputs/docker-events.md)
+  * [Docker metrics](pipeline/inputs/docker-metrics.md)
   * [Dummy](pipeline/inputs/dummy.md)
+  * [Ebpf](pipeline/inputs/ebpf.md)
   * [Elasticsearch](pipeline/inputs/elasticsearch.md)
+  * [Exec WASI](pipeline/inputs/exec-wasi.md)
   * [Exec](pipeline/inputs/exec.md)
-  * [Exec Wasi](pipeline/inputs/exec-wasi.md)
-  * [Ebpf](pipeline/inputs/ebpf.md)
-  * [Fluent Bit Metrics](pipeline/inputs/fluentbit-metrics.md)
+  * [Fluent Bit metrics](pipeline/inputs/fluentbit-metrics.md)
   * [Forward](pipeline/inputs/forward.md)
   * [Head](pipeline/inputs/head.md)
   * [Health](pipeline/inputs/health.md)
   * [HTTP](pipeline/inputs/http.md)
   * [Kafka](pipeline/inputs/kafka.md)
-  * [Kernel Logs](pipeline/inputs/kernel-logs.md)
-  * [Kubernetes Events](pipeline/inputs/kubernetes-events.md)
-  * [Memory Metrics](pipeline/inputs/memory-metrics.md)
+  * [Kernel logs](pipeline/inputs/kernel-logs.md)
+  * [Kubernetes events](pipeline/inputs/kubernetes-events.md)
+  * [Memory metrics](pipeline/inputs/memory-metrics.md)
   * [MQTT](pipeline/inputs/mqtt.md)
-  * [Network I/O Log Based Metrics](pipeline/inputs/network-io-metrics.md)
-  * [NGINX Exporter Metrics](pipeline/inputs/nginx.md)
-  * [Node Exporter Metrics](pipeline/inputs/node-exporter-metrics.md)
+  * [Network I/O metrics](pipeline/inputs/network-io-metrics.md)
+  * [NGINX exporter metrics](pipeline/inputs/nginx.md)
+  * [Node exporter metrics](pipeline/inputs/node-exporter-metrics.md)
   * [OpenTelemetry](pipeline/inputs/opentelemetry.md)
-  * [Podman Metrics](pipeline/inputs/podman-metrics.md)
-  * [Process Exporter Metrics](pipeline/inputs/process-exporter-metrics.md)
-  * [Process Log Based Metrics](pipeline/inputs/process.md)
-  * [Prometheus Remote Write](pipeline/inputs/prometheus-remote-write.md)
-  * [Prometheus Scrape Metrics](pipeline/inputs/prometheus-scrape-metrics.md)
+  * [Podman metrics](pipeline/inputs/podman-metrics.md)
+  * [Process exporter metrics](pipeline/inputs/process-exporter-metrics.md)
+  * [Process metrics](pipeline/inputs/process.md)
+  * [Prometheus remote write](pipeline/inputs/prometheus-remote-write.md)
+  * [Prometheus scrape Metrics](pipeline/inputs/prometheus-scrape-metrics.md)
   * [Random](pipeline/inputs/random.md)
-  * [Serial Interface](pipeline/inputs/serial-interface.md)
+  * [Serial interface](pipeline/inputs/serial-interface.md)
   * [Splunk](pipeline/inputs/splunk.md)
-  * [Standard Input](pipeline/inputs/standard-input.md)
+  * [Standard input](pipeline/inputs/standard-input.md)
   * [StatsD](pipeline/inputs/statsd.md)
   * [Syslog](pipeline/inputs/syslog.md)
   * [Systemd](pipeline/inputs/systemd.md)
   * [Tail](pipeline/inputs/tail.md)
   * [TCP](pipeline/inputs/tcp.md)
   * [Thermal](pipeline/inputs/thermal.md)
   * [UDP](pipeline/inputs/udp.md)
-  * [Windows Event Log](pipeline/inputs/windows-event-log.md)
-  * [Windows Event Log (winevtlog)](pipeline/inputs/windows-event-log-winevtlog.md)
-  * [Windows Exporter Metrics](pipeline/inputs/windows-exporter-metrics.md)
+  * [Windows Event logs (winevtlog)](pipeline/inputs/windows-event-log-winevtlog.md)
+  * [Windows Event logs (winlog)](pipeline/inputs/windows-event-log.md)
+  * [Windows exporter metrics](pipeline/inputs/windows-exporter-metrics.md)
 * [Parsers](pipeline/parsers/README.md)
-  * [Configuring Parser](pipeline/parsers/configuring-parser.md)
+  * [Configuring parsers](pipeline/parsers/configuring-parser.md)
   * [JSON](pipeline/parsers/json.md)
-  * [Regular Expression](pipeline/parsers/regular-expression.md)
+  * [Regular expression](pipeline/parsers/regular-expression.md)
   * [LTSV](pipeline/parsers/ltsv.md)
   * [Logfmt](pipeline/parsers/logfmt.md)
   * [Decoders](pipeline/parsers/decoders.md)
 * [Processors](pipeline/processors/README.md)
-  * [Content Modifier](pipeline/processors/content-modifier.md)
+  * [Content modifier](pipeline/processors/content-modifier.md)
   * [Labels](pipeline/processors/labels.md)
-  * [Metrics Selector](pipeline/processors/metrics-selector.md)
-  * [OpenTelemetry Envelope](pipeline/processors/opentelemetry-envelope.md)
+  * [Metrics selector](pipeline/processors/metrics-selector.md)
+  * [OpenTelemetry envelope](pipeline/processors/opentelemetry-envelope.md)
   * [Sampling](pipeline/processors/sampling.md)
   * [SQL](pipeline/processors/sql.md)
   * [Filters as processors](pipeline/processors/filters.md)
   * [Conditional processing](pipeline/processors/conditional-processing.md)
 * [Filters](pipeline/filters/README.md)
-  * [AWS Metadata](pipeline/filters/aws-metadata.md)
+  * [AWS metadata](pipeline/filters/aws-metadata.md)
   * [CheckList](pipeline/filters/checklist.md)
-  * [ECS Metadata](pipeline/filters/ecs-metadata.md)
+  * [ECS metadata](pipeline/filters/ecs-metadata.md)
   * [Expect](pipeline/filters/expect.md)
-  * [GeoIP2 Filter](pipeline/filters/geoip2-filter.md)
+  * [GeoIP2 filter](pipeline/filters/geoip2-filter.md)
   * [Grep](pipeline/filters/grep.md)
   * [Kubernetes](pipeline/filters/kubernetes.md)
-  * [Log to Metrics](pipeline/filters/log_to_metrics.md)
+  * [Logs to metrics](pipeline/filters/log_to_metrics.md)
   * [Lua](pipeline/filters/lua.md)
-  * [Parser](pipeline/filters/parser.md)
-  * [Record Modifier](pipeline/filters/record-modifier.md)
   * [Modify](pipeline/filters/modify.md)
   * [Multiline](pipeline/filters/multiline-stacktrace.md)
   * [Nest](pipeline/filters/nest.md)
   * [Nightfall](pipeline/filters/nightfall.md)
-  * [Rewrite Tag](pipeline/filters/rewrite-tag.md)
-  * [Standard Output](pipeline/filters/standard-output.md)
+  * [Parser](pipeline/filters/parser.md)
+  * [Record modifier](pipeline/filters/record-modifier.md)
+  * [Rewrite tag](pipeline/filters/rewrite-tag.md)
+  * [Standard output](pipeline/filters/standard-output.md)
   * [Sysinfo](pipeline/filters/sysinfo.md)
+  * [Tensorflow](pipeline/filters/tensorflow.md)
   * [Throttle](pipeline/filters/throttle.md)
   * [Type Converter](pipeline/filters/type-converter.md)
-  * [Tensorflow](pipeline/filters/tensorflow.md)
   * [Wasm](pipeline/filters/wasm.md)
 * [Outputs](pipeline/outputs/README.md)
   * [Amazon CloudWatch](pipeline/outputs/cloudwatch.md)
   * [Amazon Kinesis Data Firehose](pipeline/outputs/firehose.md)
   * [Amazon Kinesis Data Streams](pipeline/outputs/kinesis.md)
   * [Amazon S3](pipeline/outputs/s3.md)
+  * [Apache SkyWalking](pipeline/outputs/skywalking.md)
   * [Azure Blob](pipeline/outputs/azure_blob.md)
   * [Azure Data Explorer](pipeline/outputs/azure_kusto.md)
   * [Azure Log Analytics](pipeline/outputs/azure.md)
@@ -189,34 +190,32 @@
   * [Dynatrace](pipeline/outputs/dynatrace.md)
   * [Elasticsearch](pipeline/outputs/elasticsearch.md)
   * [File](pipeline/outputs/file.md)
-  * [FlowCounter](pipeline/outputs/flowcounter.md)
+  * [Flow counter](pipeline/outputs/flowcounter.md)
   * [Forward](pipeline/outputs/forward.md)
-  * [GELF](pipeline/outputs/gelf.md)
+  * [Graylog Extended Log Format (GELF)](pipeline/outputs/gelf.md)
   * [Google Chronicle](pipeline/outputs/chronicle.md)
   * [Google Cloud BigQuery](pipeline/outputs/bigquery.md)
   * [HTTP](pipeline/outputs/http.md)
   * [InfluxDB](pipeline/outputs/influxdb.md)
-  * [Kafka](pipeline/outputs/kafka.md)
+  * [Kafka Producer](pipeline/outputs/kafka.md)
   * [Kafka REST Proxy](pipeline/outputs/kafka-rest-proxy.md)
   * [LogDNA](pipeline/outputs/logdna.md)
   * [Loki](pipeline/outputs/loki.md)
-  * [Microsoft Fabric](pipeline/outputs/azure_kusto.md)
   * [NATS](pipeline/outputs/nats.md)
   * [New Relic](pipeline/outputs/new-relic.md)
-  * [NULL](pipeline/outputs/null.md)
+  * [Null](pipeline/outputs/null.md)
   * [Observe](pipeline/outputs/observe.md)
   * [OpenObserve](pipeline/outputs/openobserve.md)
   * [OpenSearch](pipeline/outputs/opensearch.md)
   * [OpenTelemetry](pipeline/outputs/opentelemetry.md)
-  * [Oracle Log Analytics](pipeline/outputs/oci-logging-analytics.md)
+  * [Oracle Cloud Infrastructure Logging Analytics](pipeline/outputs/oci-logging-analytics.md)
   * [PostgreSQL](pipeline/outputs/postgresql.md)
-  * [Prometheus Exporter](pipeline/outputs/prometheus-exporter.md)
-  * [Prometheus Remote Write](pipeline/outputs/prometheus-remote-write.md)
-  * [SkyWalking](pipeline/outputs/skywalking.md)
+  * [Prometheus exporter](pipeline/outputs/prometheus-exporter.md)
+  * [Prometheus remote write](pipeline/outputs/prometheus-remote-write.md)
   * [Slack](pipeline/outputs/slack.md)
   * [Splunk](pipeline/outputs/splunk.md)
   * [Stackdriver](pipeline/outputs/stackdriver.md)
-  * [Standard Output](pipeline/outputs/standard-output.md)
+  * [Standard output](pipeline/outputs/standard-output.md)
   * [Syslog](pipeline/outputs/syslog.md)
   * [TCP and TLS](pipeline/outputs/tcp-and-tls.md)
   * [Treasure Data](pipeline/outputs/treasure-data.md)

pipeline/filters/aws-metadata.md

@@ -1,4 +1,4 @@
-# AWS Metadata
+# AWS metadata
 
 The _AWS Filter_ enriches logs with AWS Metadata. The plugin adds the EC2 instance ID and availability zone to log records. To use this plugin, you must be running in EC2 and have the [instance metadata service enabled](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html).
 
@@ -188,4 +188,4 @@ The resulting logs might look like this:
 
 ```text
 {"log"=>"aws is awesome", "az"=>"us-east-1a", "ec2_instance_id"=>"i-0e66fc7f9809d7168", "Name"=>"fluent-bit-docs-example", "project"=>"fluentbit"}
-```
+```

pipeline/filters/log_to_metrics.md

@@ -2,7 +2,7 @@
 description: Generate metrics from logs
 ---
 
-# Log to metrics
+# Logs to metrics
 
 ![](https://static.scarf.sh/a.png?x-pxid=768830f6-8d2d-4231-9e5e-259ce6797ba5)
 
@@ -536,5 +536,4 @@ The `+Inf` bucket will always be included regardless of the buckets you specify.
 
 {% endhint %}
 
-This filter also attaches Kubernetes labels to each metric, identical to the behavior
-of `label_field`. This results in two sets for the histogram.
+This filter also attaches Kubernetes labels to each metric, identical to the behavior of `label_field`. This results in two sets for the histogram.

pipeline/filters/nest.md

@@ -7,8 +7,7 @@ The _Nest_ filter plugin lets you operate on or with nested data. Its modes of o
 
 ## Example usage for `nest`
 
-As an example using JSON notation, to nest keys matching the `Wildcard` value `Key*`
-under a new key `NestKey` the transformation becomes:
+As an example using JSON notation, to nest keys matching the `Wildcard` value `Key*` under a new key `NestKey` the transformation becomes:
 
 Input:
 
@@ -34,8 +33,7 @@ Output:
 
 ## Example usage for `lift`
 
-As an example using JSON notation, to lift keys nested under the `Nested_under` value
-`NestKey*` the transformation becomes:
+As an example using JSON notation, to lift keys nested under the `Nested_under` value `NestKey*` the transformation becomes:
 
 Input:
 
@@ -86,9 +84,7 @@ To start filtering records, run the filter from the command line or through the
 
 Using the command line mode requires quotes to parse the wildcard properly. The use of a configuration file is recommended.
 
-The following command loads the _mem_ plugin. Then the _nest_ filter matches the
-wildcard rule to the keys and nests the keys matching `Mem.*` under the new key
-`NEST`.
+The following command loads the _mem_ plugin. Then the _nest_ filter matches the wildcard rule to the keys and nests the keys matching `Mem.*` under the new key `NEST`.
 
 ```shell
 ./fluent-bit -i mem -p 'tag=mem.local' -F nest -p 'Operation=nest' -p 'Wildcard=Mem.*' -p 'Nest_under=Memstats' -p 'Remove_prefix=Mem.' -m '*' -o stdout
@@ -133,7 +129,7 @@ pipeline:
     Wildcard Mem.*
     Nest_under Memstats
     Remove_prefix Mem.
-    
+
  [OUTPUT]
     Name  stdout
     Match *
@@ -210,10 +206,10 @@ pipeline:
     Operation lift
     Nested_under Stats
     Remove_prefix NESTED
-    
+
 [OUTPUT]
     Name  stdout
-    Match *    
+    Match *
 ```
 
 {% endtab %}
@@ -228,8 +224,7 @@ pipeline:
 
 ## Example 3 - `nest` 3 levels deep
 
-This example takes the keys starting with `Mem.*` and nests them under `LAYER1`,
-which is then nested under `LAYER2`, which is nested under `LAYER3`.
+This example takes the keys starting with `Mem.*` and nests them under `LAYER1`, which is then nested under `LAYER2`, which is nested under `LAYER3`.
 
 ### Deep `nest` configuration file
 
@@ -453,4 +448,4 @@ pipeline:
   "Lifted3_Lifted2_Lifted1_Mem.used"=>1253912,
   "Lifted3_Lifted2_Lifted1_Mem.free"=>2796996
 }
-```
+```

pipeline/filters/nightfall.md

@@ -1,14 +1,8 @@
 # Nightfall
 
-The _Nightfall_ filter scans logs for sensitive data and redacts any sensitive
-portions. This filter supports scanning for various sensitive information, ranging
-from API keys and Personally Identifiable Information (PII) to custom regular
-expressions you define. You can configure what to scan for in the
-[Nightfall Dashboard](https://app.nightfall.ai).
+The _Nightfall_ filter scans logs for sensitive data and redacts any sensitive portions. This filter supports scanning for various sensitive information, ranging from API keys and Personally Identifiable Information (PII) to custom regular expressions you define. You can configure what to scan for in the [Nightfall Dashboard](https://app.nightfall.ai).
 
-This filter isn't enabled by default in version 1.9.0 due to a typo. To enable it,
-set the flag ```-DFLB_FILTER_NIGHTFALL=ON``` when building. This is fixed for
-versions 1.9.1 and later.
+This filter isn't enabled by default in version 1.9.0 due to a typo. To enable it, set the flag ```-DFLB_FILTER_NIGHTFALL=ON``` when building. This is fixed for versions 1.9.1 and later.
 
 ## Configuration parameters
 
@@ -44,7 +38,7 @@ pipeline:
           policy_id: 5991946b-1cc8-4c38-9240-72677029a3f7
           sampling_rate: 1
           tls.ca_path: /etc/ssl/certs
-    
+
     outputs:
         - name: stdout
           match: '*'
@@ -104,4 +98,4 @@ Which results in output like:
 [0] app.log: [1644464790.280412000, {"A"=>"there is nothing sensitive here", "B"=>[{"A"=>"my credit card number is *******************"}, {"A"=>"*********** is my social security."}], "C"=>false, "D"=>"key ********************"}]
 [2022/02/09 19:47:25] [ info] [filter:nightfall:nightfall.0] Nightfall request http_do=0, HTTP Status: 200
 [0] app.log: [1644464845.675431000, {"A"=>"a very safe string"}]
-```
+```

pipeline/filters/parser.md

@@ -139,8 +139,7 @@ You can see the records `{"data":"100 0.5 true This is example"}` are parsed.
 
 By default, the parser plugin only keeps the parsed fields in its output.
 
-If you enable `Reserve_Data`, all other fields are preserved. First the contents of the corresponding parsers file, 
-depending on the choice for YAML or classic configurations, would be as follows:
+If you enable `Reserve_Data`, all other fields are preserved. First the contents of the corresponding parsers file, depending on the choice for YAML or classic configurations, would be as follows:
 
 {% tabs %}
 {% tab title="parsers.yaml" %}
@@ -210,7 +209,7 @@ pipeline:
     Key_Name data
     Parser dummy_test
     Reserve_Data On
-    
+
  [OUTPUT]
     Name stdout
     Match *
@@ -255,8 +254,7 @@ ______ _                  _    ______ _ _             ___  _____
 [0] dummy.data: [[1750325240.682903000, {}], {"INT"=>"100", "FLOAT"=>"0.5", "BOOL"=>"true", "STRING"=>"This is example", "key1"=>"value1", "key2"=>"value2"}]
 ```
 
-If you enable `Reserve_Data` and `Preserve_Key`, the original key field will also be preserved. First the contents of 
-the corresponding parsers file, depending on the choice for YAML or classic configurations, would be as follows:
+If you enable `Reserve_Data` and `Preserve_Key`, the original key field will also be preserved. First the contents of the corresponding parsers file, depending on the choice for YAML or classic configurations, would be as follows:
 
 {% tabs %}
 {% tab title="parsers.yaml" %}
@@ -328,7 +326,7 @@ pipeline:
     Parser dummy_test
     Reserve_Data On
     Preserve_Key On
-    
+
  [OUTPUT]
     Name stdout
     Match *
@@ -371,4 +369,4 @@ ______ _                  _    ______ _ _             ___  _____
 [0] dummy.data: [[1750325678.572817000, {}], {"INT"=>"100", "FLOAT"=>"0.5", "BOOL"=>"true", "STRING"=>"This is example", "data"=>"100 0.5 true This is example", "key1"=>"value1", "key2"=>"value2"}]
 [0] dummy.data: [[1750325679.574538000, {}], {"INT"=>"100", "FLOAT"=>"0.5", "BOOL"=>"true", "STRING"=>"This is example", "data"=>"100 0.5 true This is example", "key1"=>"value1", "key2"=>"value2"}]
 [0] dummy.data: [[1750325680.569750000, {}], {"INT"=>"100", "FLOAT"=>"0.5", "BOOL"=>"true", "STRING"=>"This is example", "data"=>"100 0.5 true This is example", "key1"=>"value1", "key2"=>"value2"}]
-```
+```

pipeline/filters/record-modifier.md

@@ -16,8 +16,7 @@ The plugin supports the following configuration parameters:
 
 ## Get started
 
-To start filtering records, run the filter from the command line or through a
-configuration file.
+To start filtering records, run the filter from the command line or through a configuration file.
 
 This is a sample `in_mem` record to filter.
 
@@ -27,8 +26,7 @@ This is a sample `in_mem` record to filter.
 
 ### Append fields
 
-The following configuration file appends a product name and hostname to a record
-using an environment variable:
+The following configuration file appends a product name and hostname to a record using an environment variable:
 
 {% tabs %}
 {% tab title="fluent-bit.yaml" %}

pipeline/filters/rewrite-tag.md

@@ -2,7 +2,7 @@
 description: Powerful and flexible routing
 ---
 
-# Rewrite Tag
+# Rewrite tag
 
 Tags make [routing](../../concepts/data-pipeline/router.md) possible. Tags are set in the configuration of the `INPUT` definitions where the records are generated. There are scenarios where you might want to modify the tag in the pipeline to perform more advanced and flexible routing.
 
@@ -253,4 +253,4 @@ The records generated are handled by the internal emitter, so the new records ar
 
 The _Emitter_ is an internal Fluent Bit plugin that allows other components of the pipeline to emit custom records. On this case `rewrite_tag` creates an emitter instance to use it exclusively to emit records, allowing for granular control of who is emitting what.
 
-Change the Emitter name in the metrics by adding the `Emitter_Name` configuration property described previously.
+Change the Emitter name in the metrics by adding the `Emitter_Name` configuration property described previously.