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: installation/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
@@ -28,7 +28,7 @@ The recommended way to deploy Fluent Bit for Kubernetes is with the official [He
28
28
29
29
If you are using Red Hat OpenShift you must set up Security Context Constraints (SCC) using the relevant option in the helm chart.
30
30
31
-
### Installing with Helm Chart
31
+
### Installing with Helm chart
32
32
33
33
[Helm](https://helm.sh) is a package manager for Kubernetes and lets you deploy application packages into your running cluster. Fluent Bit is distributed using a Helm chart found in the [Fluent Helm Charts repository](https://github.com/fluent/helm-charts).
Copy file name to clipboardExpand all lines: installation/upgrade-notes.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,13 +16,13 @@ The `td-agent-bit` package is no longer provided after this release. Users shoul
16
16
17
17
If you are migrating from previous version of Fluent Bit, review the following important changes:
18
18
19
-
### Tail Input Plugin
19
+
### Tail input plugin
20
20
21
21
By default, the tail input plugin follows a file from the end after the service starts, instead of reading it from the beginning. Every file found when the plugin starts is followed from it last position. New files discovered at runtime or when files rotate are read from the beginning.
22
22
23
23
To keep the old behavior, set the option `read_from_head` to `true`.
24
24
25
-
### Stackdriver Output Plugin
25
+
### Stackdriver output plugin
26
26
27
27
The `project_id` of [resource](https://cloud.google.com/logging/docs/reference/v2/rest/v2/MonitoredResource) in [LogEntry](https://cloud.google.com/logging/docs/reference/v2/rest/v2/LogEntry) sent to Google Cloud Logging would be set to the `project_id` rather than the project number. To learn the difference between Project ID and project number, see [Creating and managing projects](https://cloud.google.com/resource-manager/docs/creating-managing-projects#before_you_begin).
28
28
@@ -44,15 +44,15 @@ If you are migrating from Fluent Bit v1.2 to v1.3, there are no breaking changes
44
44
45
45
## Fluent Bit v1.2
46
46
47
-
### Docker, JSON, Parsers and Decoders
47
+
### Docker, JSON, parsers, and decoders
48
48
49
49
Fluent Bit v1.2 fixed many issues associated with JSON encoding and decoding.
50
50
51
51
For example, when parsing Docker logs, it's no longer necessary to use decoders. The new Docker parser looks like this:
52
52
53
53
```python [PARSER] Name docker Format json Time_Key time Time_Format %Y-%m-%dT%H:%M:%S.%L Time_Keep On ```
54
54
55
-
### Kubernetes Filter
55
+
### Kubernetes filter
56
56
57
57
Fluent Bit made improvements to Kubernetes Filter handling of stringified `log` messages. If the `Merge_Log` option is enabled, it will try to handle the log content as a JSON map, if so, it will add the keys to the root map.
These are now using the Github Actions built versions. Legacy AppVeyor builds are still available (AMD 32/64 only) at releases.fluentbit.io but are deprecated.
To check the integrity, use the `Get-FileHash` cmdlet for PowerShell.
104
104
@@ -164,10 +164,10 @@ Fluent Bit v2.0.x
164
164
165
165
To halt the process, press `Control+C` in the terminal.
166
166
167
-
## Installing from the EXE installer
167
+
## Installing from the executable installer
168
168
169
-
1. Download an EXE installer for the appropriate 32-bit or 64-bit build.
170
-
1. Double-click the EXE installer you've downloaded. The installation wizard starts.
169
+
1. Download an `EXE` installer for the appropriate 32-bit or 64-bit build.
170
+
1. Double-click the `EXE` installer you've downloaded. The installation wizard starts.
171
171
172
172
1. Click **Next** and finish the installation. By default, Fluent Bit is installed in `C:\Program Files\fluent-bit\`.
173
173
@@ -189,7 +189,7 @@ The uninstaller also supports a silent uninstall using the same `/S` flag. This
189
189
190
190
## Windows service support
191
191
192
-
Windows services are equivalent to daemons in UNIX (long-running background processes). For v1.5.0 and later, Fluent Bit has native support for Windows services.
192
+
Windows services are equivalent to daemons in Unix (long-running background processes). For v1.5.0 and later, Fluent Bit has native support for Windows services.
193
193
194
194
For example, you have the following installation layout:
195
195
@@ -279,7 +279,7 @@ Remove the service (requires PowerShell 6.0 or later)
279
279
Remove-Service fluent-bit
280
280
```
281
281
282
-
## Compile from Source
282
+
## Compile from source
283
283
284
284
If you need to create a custom executable, use the following procedure to compile Fluent Bit by yourself.
285
285
@@ -294,7 +294,7 @@ start vs.exe
294
294
295
295
1. Choose `C++ Build Tools` and `C++ CMake tools for Windows` and wait until the process finishes.
296
296
297
-
1. Install flex and bison. One way to install them on Windows is to use [winflexbison](https://github.com/lexxmark/winflexbison).
297
+
1. Install flex and bison. One way to install them on Windows is to use [`winflexbison`](https://github.com/lexxmark/winflexbison).
Copy file name to clipboardExpand all lines: installation/yocto-embedded-linux.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,11 +6,11 @@ Fluent Bit distributes two main recipes, one for testing/dev purposes and one wi
6
6
7
7
| Version | Recipe | Description |
8
8
| :--- | :--- | :--- |
9
-
|`devel`|[fluent-bit\_git.bb](https://github.com/fluent/fluent-bit/blob/master/fluent-bit_git.bb)| Build Fluent Bit from Git master. Use for development and testing purposes only. |
10
-
|`v1.8.11`|[fluent-bit\_1.8.11.bb](https://github.com/fluent/fluent-bit/blob/v1.8.11/fluent-bit_1.8.11.bb)| Build latest stable version of Fluent Bit. |
9
+
|`devel`|[fluent-bit_git.bb](https://github.com/fluent/fluent-bit/blob/master/fluent-bit_git.bb)| Build Fluent Bit from Git master. Use for development and testing purposes only. |
10
+
|`v1.8.11`|[fluent-bit_1.8.11.bb](https://github.com/fluent/fluent-bit/blob/v1.8.11/fluent-bit_1.8.11.bb)| Build latest stable version of Fluent Bit. |
11
11
12
12
It's strongly recommended to always use the stable release of the Fluent Bit recipe and not the one from Git master for production deployments.
13
13
14
14
## Fluent Bit and other architectures
15
15
16
-
Fluent Bit >= v1.1.x fully supports `x86_64`, `x86`, `arm32v7`, and `arm64v8`.
16
+
Fluent Bit 1.1.x and later fully supports `x86_64`, `x86`, `arm32v7`, and `arm64v8`.
0 commit comments