Merge pull request #2372 from fluent/lynettemiles/sc-162129/fb-broken-links

Author: esmerel

administration/configuring-fluent-bit/yaml/upstream-servers-section.md

@@ -1,6 +1,6 @@
 # Upstream servers
 
-The `upstream_servers` section of YAML configuration files defines a group of endpoints, referred to as nodes. Nodes are used by output plugins to distribute data in a round-robin fashion. Use this section for plugins that require load balancing when sending data. Examples of plugins that support this capability include [Forward](../../../pipeline/outputs/forward.md) and [Elasticsearch](../../../pipeline/outputs/elasticsearch).
+The `upstream_servers` section of YAML configuration files defines a group of endpoints, referred to as nodes. Nodes are used by output plugins to distribute data in a round-robin fashion. Use this section for plugins that require load balancing when sending data. Examples of plugins that support this capability include [Forward](../../../pipeline/outputs/forward.md) and [Elasticsearch](../../../pipeline/outputs/elasticsearch.md).
 
 The `upstream_servers` section require specifying a `name` for the group and a list
 of `nodes`. The following example defines two upstream server groups, `forward-balancing` and `forward-balancing-2`:

installation/downloads/aws-container.md

@@ -7,20 +7,20 @@ AWS maintains a distribution of Fluent Bit that combines the latest official rel
 The [AWS for Fluent Bit](https://github.com/aws/aws-for-fluent-bit) image contains Go Plugins for:
 
 - Amazon CloudWatch as `cloudwatch_logs`. See the
-  [Fluent Bit docs](../../pipeline/outputs/cloudwatch) or the
+  [Fluent Bit docs](../../pipeline/outputs/cloudwatch.md) or the
   [Plugin repository](https://github.com/aws/amazon-cloudwatch-logs-for-fluent-bit).
 - Amazon Kinesis Data Firehose as `kinesis_firehose`. See the
-  [Fluent Bit docs](../../pipeline/outputs/firehose) or the
+  [Fluent Bit docs](../../pipeline/outputs/firehose.md) or the
   [Plugin repository](https://github.com/aws/amazon-kinesis-firehose-for-fluent-bit).
 - Amazon Kinesis Data Streams as `kinesis_streams`. See the
-  [Fluent Bit docs](../../pipeline/outputs/kinesis) or the
+  [Fluent Bit docs](../../pipeline/outputs/kinesis.md) or the
   [Plugin repository](https://github.com/aws/amazon-kinesis-streams-for-fluent-bit).
 
 These plugins are higher performance than Go plugins.
 
 Also, Fluent Bit includes an S3 output plugin named `s3`.
 
-- [Amazon S3](../../pipeline/outputs/s3)
+- [Amazon S3](../../pipeline/outputs/s3.md)
 
 ## Versions and regional repositories
 

installation/downloads/kubernetes.md

@@ -14,7 +14,7 @@ description: Kubernetes Production Grade Log Processor
 
 Before getting started it's important to understand how Fluent Bit will be deployed. Kubernetes manages a cluster of nodes. The Fluent Bit log agent tool needs to run on every node to collect logs from every pod. Fluent Bit is deployed as a DaemonSet, which is a pod that runs on every node of the cluster.
 
-When Fluent Bit runs, it reads, parses, and filters the logs of every pod. In addition, Fluent Bit adds metadata to each entry using the [Kubernetes](../../pipeline/filters/kubernetes) filter plugin.
+When Fluent Bit runs, it reads, parses, and filters the logs of every pod. In addition, Fluent Bit adds metadata to each entry using the [Kubernetes](../../pipeline/filters/kubernetes.md) filter plugin.
 
 The Kubernetes filter plugin talks to the Kubernetes API Server to retrieve relevant information such as the `pod_id`, `labels`, and `annotations`. Other fields, such as `pod_name`, `container_id`, and `container_name`, are retrieved locally from the log file names. All of this is handled automatically, and no intervention is required from a configuration aspect.
 

installation/downloads/macos.md

@@ -163,7 +163,7 @@ To make the access path easier to Fluent Bit binary, extend the `PATH` variable:
 export PATH=/opt/fluent-bit/bin:$PATH
 ```
 
-To test, try Fluent Bit by generating a test message using the [Dummy input plugin](../../pipeline/inputs/dummy) which prints to the standard output interface every one second:
+To test, try Fluent Bit by generating a test message using the [Dummy input plugin](../../pipeline/inputs/dummy.md) which prints to the standard output interface every one second:
 
 ```shell
 fluent-bit -i dummy -o stdout -f 1

pipeline/filters/multiline-stacktrace.md

@@ -40,7 +40,7 @@ The plugin supports the following configuration parameters:
 
 | Property | Description |
 | -------- | ----------- |
-| `multiline.parser` | Specify one or multiple [Multiline Parser definitions](../pipeline/parsers/multiline-parsing.md) to apply to the content. You can specify multiple multiline parsers to detect different formats by separating them with a comma. |
+| `multiline.parser` | Specify one or multiple [Multiline Parser definitions](../../pipeline/parsers/multiline-parsing.md) to apply to the content. You can specify multiple multiline parsers to detect different formats by separating them with a comma. |
 | `multiline.key_content` | Key name that holds the content to process. A multiline parser definition can specify the `key_content` This option allows for overwriting that value for the purpose of the filter. |
 | `mode` | Mode can be `parser` for regular expression concatenation, or `partial_message` to concatenate split Docker logs. |
 | `buffer` | Enable buffered mode. In buffered mode, the filter can concatenate multiple lines from inputs that ingest records one by one (like Forward), rather than in chunks, re-emitting them into the beginning of the pipeline (with the same tag) using the `in_emitter` instance. With buffer off, this filter won't work with most inputs, except Tail. |