Fixing remaining 404s

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

Author: esmerel

.github/workflows/links.yaml

@@ -3,7 +3,6 @@ name: Links
 on:
   repository_dispatch:
   workflow_dispatch:
-  pull_request:
   schedule:
     - cron: "00 18 * * *"
 

administration/configuring-fluent-bit/unit-sizes.md

@@ -1,6 +1,6 @@
 # Unit sizes
 
-Some configuration directives in [Fluent Bit](http://fluentbit.io) refer to unit sizes such as when defining the size of a buffer or specific limits. Plugins like [Tail Input](../../pipeline/inputs/tail.md), [Forward Input](../../pipeline/inputs/forward.md) or generic properties like [`Mem_Buf_Limit`](../backpressure.md) use unit sizes.
+Some configuration directives in [Fluent Bit](http://fluentbit.io) refer to unit sizes such as when defining the size of a buffer or specific limits. Plugins like [Tail Input](../../pipeline/inputs/tail.md), [Forward Input](../../pipeline/inputs/forward.md), or generic properties like [`Mem_Buf_Limit`](../backpressure.md) use unit sizes.
 
 Fluent Bit v0.11.10 standardized unit sizes across the core and plugins. The following table describes the options that can be used and what they mean:
 

concepts/data-pipeline/parser.md

@@ -26,7 +26,7 @@ The parser converts unstructured data to structured data. As an example, conside
 192.168.2.20 - - [28/Jul/2006:10:27:10 -0300] "GET /cgi-bin/try/ HTTP/1.0" 200 3395
 ```
 
-This log line is a raw string without format. Structuring the log makes it easier to process the data later. If the [regular expression parser](../../pipeline/parsers/regular-expression) is used, the log entry could be converted to:
+This log line is a raw string without format. Structuring the log makes it easier to process the data later. If the [regular expression parser](../../pipeline/parsers/regular-expression.md) is used, the log entry could be converted to:
 
 ```javascript
 {

local-testing/validating-your-data-and-structure.md

@@ -4,7 +4,7 @@ Fluent Bit supports multiple sources and formats. In addition, it provides filte
 
 Fluent Bit users are encouraged to integrate data validation in their continuous integration (CI) systems.
 
-In a normal production environment, inputs, filters, and outputs are defined in configuration files. Fluent Bit provides the [Expect](../pipeline/filters/expect) filter, which you can use to validate keys and values from your records and take action when an exception is found.
+In a normal production environment, inputs, filters, and outputs are defined in configuration files. Fluent Bit provides the [Expect](../pipeline/filters/expect.md) filter, which you can use to validate keys and values from your records and take action when an exception is found.
 
 A simplified view of the data processing pipeline is as follows:
 
@@ -20,8 +20,8 @@ IS --> Fil --> OD
 
 Consider the following pipeline, which uses a JSON file as its data source and has two filters:
 
-- [Grep](../pipeline/filters/grep) to exclude certain records.
-- [Record Modifier](../pipeline/filters/record-modifier) to alter records' content by adding and removing specific keys.
+- [Grep](../pipeline/filters/grep.md) to exclude certain records.
+- [Record Modifier](../pipeline/filters/record-modifier.md) to alter records' content by adding and removing specific keys.
 
 ```mermaid
 flowchart LR
@@ -37,7 +37,7 @@ record --> stdout
 
 Add data validation between each step to ensure your data structure is correct.
 
-This example uses the [Expect](../pipeline/filters/expect) filter.
+This example uses the [Expect](../pipeline/filters/expect.md) filter.
 
 ```mermaid
 flowchart LR
@@ -164,7 +164,7 @@ The following is the Fluent Bit classic parsers file:
 {% endtab %}
 {% endtabs %}
 
-If the JSON parser fails or is missing in the [Tail](../pipeline/inputs/tail) input (`parser json`), the Expect filter triggers the `exit` action.
+If the JSON parser fails or is missing in the [Tail](../pipeline/inputs/tail.md) input (`parser json`), the Expect filter triggers the `exit` action.
 
 To extend the pipeline, add a Grep filter to match records that map `label` containing a key called `name` with value the `abc`, and add an Expect filter to re-validate that condition:
 

pipeline/filters/grep.md

@@ -39,7 +39,7 @@ To start filtering records, run the filter from the command line or through the
 
 When using the command line, pay close attention to quote the regular expressions. Using a configuration file might be easier.
 
-The following command loads the [tail](../../pipeline/inputs/tail) plugin and reads the content of `lines.txt`. Then the `grep` filter applies a regular expression rule over the `log` field created by the `tail` plugin and only passes records with a field value starting with `aa`:
+The following command loads the [tail](../../pipeline/inputs/tail.md) plugin and reads the content of `lines.txt`. Then the `grep` filter applies a regular expression rule over the `log` field created by the `tail` plugin and only passes records with a field value starting with `aa`:
 
 ```shell
 fluent-bit -i tail -p 'path=lines.txt' -F grep -p 'regex=log aa' -m '*' -o stdout

pipeline/inputs/process.md

@@ -2,7 +2,7 @@
 
 The _Process metrics_ input plugin lets you check how healthy a process is. It does so by performing service checks at specified intervals.
 
-This plugin creates metrics that are log-based, such as JSON payloads. For Prometheus-based metrics, see the [Node exporter metrics](./node-exporter-metrics) input plugin.
+This plugin creates metrics that are log-based, such as JSON payloads. For Prometheus-based metrics, see the [Node exporter metrics](./node-exporter-metrics.md) input plugin.
 
 ## Configuration parameters
 
@@ -16,7 +16,7 @@ The plugin supports the following configuration parameters:
 | `Alert`         | If enabled, the plugin will only generate messages if the target process is down.                             | `false` |
 | `Fd`            | If enabled, a number of `fd` is appended to each record.                                                      | `true`  |
 | `Mem`           | If enabled, memory usage of the process is appended to each record.                                           | `true`  |
-| `Threaded`      | Specifies whether to run this input in its own [thread](../../administration/multithreading#inputs).       | `false` |
+| `Threaded`      | Specifies whether to run this input in its own [thread](../../administration/multithreading.md#inputs).       | `false` |
 
 ## Get started
 

pipeline/outputs/azure_kusto.md

@@ -26,7 +26,7 @@ Fluent Bit uses the application's credentials to ingest data into your cluster.
 
 - [Register an application](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app#register-an-application)
 - [Add a client secret](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app#add-a-client-secret)
-- [Authorize the app in your database](https://docs.microsoft.com/en-us/azure/data-explorer/kusto/management/access-control/principals-and-identity-providers#azure-ad-tenants)
+- [Authorize the app in your database](https://learn.microsoft.com/en-us/azure/app-service/overview-authentication-authorization)
 
 ## Create a table
 
@@ -70,7 +70,7 @@ By default, Kusto will insert incoming ingestion data into a table by inferring
 | `buffering_enabled` | Optional. Enable buffering into disk before ingesting into Azure Kusto. | `Off` |
 | `buffer_dir` | Optional. When buffering is `On`, specifies the location of directory where the buffered data will be stored. | `/tmp/fluent-bit/azure-kusto/` |
 | `upload_timeout` | Optional. When buffering is `On`, specifies a timeout for uploads. Fluent Bit will start ingesting buffer files which have been created more than x minutes and haven't reached `upload_file_size` limit. | `30m` |
-| `upload_file_size`| Optional. When buffering is `On`, specifies the size of files to be uploaded in MBs. | `200MB` |
+| `upload_file_size`| Optional. When buffering is `On`, specifies the size of files to be uploaded in megabytes. | `200MB` |
 | `azure_kusto_buffer_key` | Optional. When buffering is `On`, set the Azure Kusto buffer key which must be specified when using multiple instances of Azure Kusto output plugin and buffering is enabled. | `key` |
 | `store_dir_limit_size` | Optional. When buffering is `On`, set the max size of the buffer directory. | `8GB` |
 | `buffer_file_delete_early`    | Optional. When buffering is `On`, whether to delete the buffered file early after successful blob creation. | `Off` |

pipeline/outputs/logdna.md

@@ -18,7 +18,6 @@ This plugin uses the following configuration parameters:
 | `tags` | A list of comma-separated strings to group records in LogDNA and simplify the query with filters. | _none_ |
 | `file` | Optional name of a file being monitored. This value is only set if the record doesn't contain a reference to it. | _none_ |
 | `app` | Name of the application. This value is automatically discovered on each record. If no value is found, the default value is used. | `Fluent Bit` |
-| `workers` | The number of [workers](../../administration/multithreading#outputs) to perform flush operations for this output. | `0` |
 
 ## Data discovery and enrichment
 

pipeline/outputs/new-relic.md

@@ -10,7 +10,7 @@ The _New Relic_ output plugin lets you send logs to New Relic.
 | `api_key` | Your [New Relic API key](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/). Either an `api_key` or `license_key` is required.| _none_ |
 | `license_key` | Your [New Relic license key](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/). Either an `api_key` or `license_key` is required. | _none_ |
 | `compress` | Sets the compression mechanism for the payload. Possible values: `gzip` or `false`. | `gzip` |
-| `workers` | Sets the number of [workers](../administration/multithreading.md#outputs) to perform flush operations for this output. | `0` |
+| `workers` | Sets the number of [workers](../../administration/multithreading.md#outputs) to perform flush operations for this output. | `0` |
 
 ## Example configuration
 

pipeline/outputs/observe.md

@@ -8,7 +8,7 @@ The following HTTP configuration parameters are relevant to Observe:
 
 | Key | Description | Default |
 | --- | ----------- | ------- |
-| `host` | IP address or hostname of the Observe data collection endpoint. Replace `$(OBSERVE_CUSTOMER)` with your [Customer ID](https://docs.observeinc.com/en/latest/content/common-topics/HelpfulHints.html?highlight=customer%20id#customer-id). | `OBSERVE_CUSTOMER.collect.observeinc.com` |
+| `host` | IP address or hostname of the Observe data collection endpoint. Replace `$(OBSERVE_CUSTOMER)` with your [Customer ID](https://docs.observeinc.com/en/latest/content/hints/CustomerId.html). | `OBSERVE_CUSTOMER.collect.observeinc.com` |
 | `port` | TCP port to use when sending data to Observe. | `443` |
 | `tls` | Specifies whether to use TLS. | `on` |
 | `uri` | Specifies the HTTP URI for Observe. | `/v1/http/fluentbit` |