You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: development/wasm-filter-plugins.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Fluent Bit supports the following Wasm tool chains:
32
32
33
33
## Get started
34
34
35
-
As described in the general options in the [source installation](../installation/sources/build-and-install.md) guide, Wasm support is enabled by default. Compile Fluent Bit with Wasm support, for example:
35
+
As described in the general options in the [source installation](../installation/downloads/source/build-and-install.md) guide, Wasm support is enabled by default. Compile Fluent Bit with Wasm support, for example:
Copy file name to clipboardExpand all lines: installation/downloads/kubernetes.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ The default configuration of Fluent Bit ensures the following:
55
55
- Consume all containers logs from the running node and parse them with either the `docker` or `cri` multi-line parser.
56
56
- Persist how far it got into each file it's tailing so if a pod is restarted it picks up from where it left off.
57
57
- The Kubernetes filter adds Kubernetes metadata, specifically `labels` and `annotations`. The filter only contacts the API Server when it can't find the cached information, otherwise it uses the cache.
58
-
- The default backend in the configuration is Elasticsearch set by the [Elasticsearch Output Plugin](../pipeline/outputs/elasticsearch.md). It uses the Logstash format to ingest the logs. If you need a different `Index` and `Type`, refer to the plugin option and update as needed.
58
+
- The default backend in the configuration is Elasticsearch set by the [Elasticsearch Output Plugin](../../pipeline/outputs/elasticsearch.md). It uses the Logstash format to ingest the logs. If you need a different `Index` and `Type`, refer to the plugin option and update as needed.
59
59
- There is an option called `Retry_Limit`, which is set to `False`. If Fluent Bit can't flush the records to Elasticsearch, it will retry indefinitely until it succeeds.
Copy file name to clipboardExpand all lines: installation/downloads/linux.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ The GPG Key fingerprint of the old key is:
33
33
F209 D876 2A60 CD49 E680 633B 4FF8 368B 6EA0 722A
34
34
```
35
35
36
-
Refer to the [supported platform documentation](supported-platforms.md) to see which platforms are supported in each release.
36
+
Refer to the [supported platform documentation](../getting-started-with-fluent-bit.md#supported-platforms-and-packages) to see which platforms are supported in each release.
Output plugins let you flush the information to some external interface, service, or terminal. The following table describes the output plugins available:
194
194
195
195
| Option | Description | Default |
196
196
| :--- | :--- | :--- |
197
-
|[`FLB_OUT_AZURE`](../../pipeline/outputs/azure.md)| Enable Microsoft Azure output plugin |`On`|
Copy file name to clipboardExpand all lines: installation/downloads/source/build-with-static-configuration.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ The following steps assume you are familiar with configuring Fluent Bit using te
12
12
13
13
#### Configuration directory
14
14
15
-
In your file system, prepare a specific directory that will be used as an entry point for the build system to lookup and parse the configuration files. This directory must contain a minimum of one configuration file, called `fluent-bit.conf`, that contains the required [`SERVICE`](/administration/configuring-fluent-bit/yaml/service-section.md), [`INPUT`](../../pipeline/inputs.md), and [`OUTPUT`](../../pipeline/outputs.md) sections.
15
+
In your file system, prepare a specific directory that will be used as an entry point for the build system to lookup and parse the configuration files. This directory must contain a minimum of one configuration file, called `fluent-bit.conf`, that contains the required [`SERVICE`](../../../administration/configuring-fluent-bit/yaml/service-section.md), [`INPUT`](../../../pipeline/inputs.md), and [`OUTPUT`](../../../pipeline/outputs.md) sections.
16
16
17
17
As an example, create a new `fluent-bit.yaml` file or `fluent-bit.conf` file:
0 commit comments