Fixing bad links

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

Author: esmerel

pipeline/filters/checklist.md

@@ -9,7 +9,7 @@ The plugin supports the following configuration parameters
 | Key | Description | Default |
 | :-- | :---------- | :------ |
 | `file` | The single value file that Fluent Bit will use as a lookup table to determine if the specified `lookup_key` exists. | _none_ |
-| `lookup_key` | The specific key to look up and determine if it exists. Supports [record accessor](../../administration/configuring-fluent-bit/classic-mode/record-accessor). | _none_ |
+| `lookup_key` | The specific key to look up and determine if it exists. Supports [record accessor](../../administration/configuring-fluent-bit/classic-mode/record-accessor.md). | _none_ |
 | `record` | The record to add if the `lookup_key` is found in the specified `file`. You can add multiple record parameters. | _none_ |
 | `mode` | Set the check mode. `exact` and `partial` are supported. | `exact`|
 | `print_query_time` | Print to stdout the elapsed query time for every matched record. | `false` |

pipeline/filters/log_to_metrics.md

@@ -26,9 +26,9 @@ The plugin supports the following configuration parameters:
 | `metric_description` | Required. Sets a description for the metric. |  |
 | `bucket` | Required for mode `histogram`. Defines a bucket for histograms. | For example, `0.75` |
 | `add_label` | Adds a custom label `NAME` and set the value to the value of `KEY`. |  |
-| `label_field` | Includes a record field as label dimension in the metric. | Name of record key. Supports [record accessor](../../administration/configuring-fluent-bit/classic-mode/record-accessor) notation for nested fields. |
-| `value_field` | Required for modes `gauge` and `histogram`. Specifies the record field that holds a numerical value. | Name of record key. Supports [record accessor](../../administration/configuring-fluent-bit/classic-mode/record-accessor) notation for nested fields. |
-| `kubernetes_mode` | If enabled, adds `pod_id`, `pod_name`, `namespace_name`, `docker_id` and `container_name` to the metric as labels. This option is intended to be used in combination with the [Kubernetes](./kubernetes) filter plugin, which fills those fields. |  |
+| `label_field` | Includes a record field as label dimension in the metric. | Name of record key. Supports [record accessor](../../administration/configuring-fluent-bit/classic-mode/record-accessor.md) notation for nested fields. |
+| `value_field` | Required for modes `gauge` and `histogram`. Specifies the record field that holds a numerical value. | Name of record key. Supports [record accessor](../../administration/configuring-fluent-bit/classic-mode/record-accessor.md) notation for nested fields. |
+| `kubernetes_mode` | If enabled, adds `pod_id`, `pod_name`, `namespace_name`, `docker_id` and `container_name` to the metric as labels. This option is intended to be used in combination with the [Kubernetes](./kubernetes.md) filter plugin, which fills those fields. |  |
 | `Regex` | Includes records in which the content of `KEY` matches the regular expression. | `KEY REGEX` |
 | `Exclude` | Excludes records in which the content of `KEY` matches the regular expression. | `KEY REGEX` |
 | `Flush_Interval_Sec` | The interval for metrics emission, in seconds. If `Flush_Interval_Sec` and `Flush_Interval_Nsec` are either both unset or both set to `0`, the filter emits metrics immediately after each filter match. Otherwise, if either parameter is set to a non-zero value, the filter emits metrics at the specified interval. Longer intervals help lower resource consumption in high-load situations. Default value: `0`. |  |

pipeline/outputs/kinesis.md

@@ -10,7 +10,7 @@ This is the documentation for the core Fluent Bit Kinesis plugin written in C. I
 
 This `kinesis_streams` plugin always uses a random partition key when uploading records to Kinesis through the [PutRecords API](https://docs.aws.amazon.com/kinesis/latest/APIReference/API_PutRecords.html).
 
-For information about how AWS credentials are fetched, see [AWS credentials](../../administration/aws-credentials).
+For information about how AWS credentials are fetched, see [AWS credentials](../../administration/aws-credentials.md).
 
 ## Configuration parameters
 

pipeline/outputs/observe.md

@@ -1,6 +1,6 @@
 # Observe
 
-Use the [HTTP output plugin](./http) to flush your records [into Observe](https://docs.observeinc.com/en/latest/content/data-ingestion/forwarders/fluentbit.html). It issues a POST request with the data records in [MessagePack](http://msgpack.org) (or JSON) format.
+Use the [HTTP output plugin](`http`) to flush your records [into Observe](https://docs.observeinc.com/en/latest/content/data-ingestion/forwarders/fluentbit.html). It issues a POST request with the data records in [MessagePack](http://msgpack.org) (or JSON) format.
 
 ## Configuration parameters
 

pipeline/outputs/standard-output.md

@@ -17,7 +17,7 @@ The _standard output_ plugin prints ingested data to standard output.
 fluent-bit -i cpu -o stdout -v
 ```
 
-This example directs the plugin to gather [CPU](../inputs/cpu-metrics) usage metrics and print them out to the standard output in a human-readable way:
+This example directs the plugin to gather [CPU](../inputs/cpu-metrics.md) usage metrics and print them out to the standard output in a human-readable way:
 
 ```shell
 fluent-bit -i cpu -o stdout -p format=msgpack -v

pipeline/processors/README.md

@@ -6,7 +6,7 @@ Additionally, filters can be implemented in a way that mimics the behavior of pr
 
 {% hint style="info" %}
 
-Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml/configuration-file) support processors.
+Only [YAML configuration files](../../administration/configuring-fluent-bit/yaml/configuration-file.md) support processors.
 
 {% endhint %}