GitBook: [1.4] 117 pages modified

Author: edsiper

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

@@ -7,7 +7,7 @@ Starting from [Fluent Bit](http://fluentbit.io) v0.11.10, all unit sizes have be
 | Suffix | Description | Example |
 | :--- | :--- | :--- |
 |  | When a suffix is **not** specified, it's assumed that the value given is a bytes representation. | Specifying a value of 32000, means 32000 bytes |
-| k, K, KB, kb | Kilobyte: a unit of memory equal to 1,000 bytes. | 32k means 32000 bytes. |
-| m, M, MB, mb | Megabyte: a unit of memory equal to 1,000,000 bytes | 1M means 1000000 bytes |
-| g, G, GB, gb | Gigabyte: a unit of memory equal to 1,000,000,000 bytes | 1G means 1000000000 bytes |
+| k, K, KB, kb | Kilobyte: a unit of memory equal to 1,000 bytes. | 32k means 3278 bytes. |
+| m, M, MB, mb | Megabyte: a unit of memory equal to 1,000,000 bytes | 1M means 1024000 bytes |
+| g, G, GB, gb | Gigabyte: a unit of memory equal to 1,000,000,000 bytes | 1G means 1024000000 bytes |
 

installation/docker.md

@@ -8,17 +8,17 @@ The following table describe the tags are available on Docker Hub [fluent/fluent
 
 | Tag\(s\) | Manifest Architectures | Description |
 | :--- | :--- | :--- |
-| 1.3 | x86\_64, arm64v8, arm32v7 | Latest release of 1.3.x series. |
-| 1.3.0 | x86\_64, arm64v8, arm32v7 | Release [v1.3.0](https://fluentbit.io/announcements/v1.3.0) |
-| 1.3-debug, 1.3.0-debug | x86\_64 | v1.3.x releases + Busybox |
+| 1.4 | x86\_64, arm64v8, arm32v7 | Latest release of 1.4.x series. |
+| 1.4.0 | x86\_64, arm64v8, arm32v7 | Release [v1.4.0](https://fluentbit.io/announcements/v1.4.0) |
+| 1.4-debug, 1.4.0-debug | x86\_64 | v1.4.x releases + Busybox |
 
 It's strongly suggested that you always use the latest image of Fluent Bit.
 
 ## Multi Architecture Images
 
-Our x86_64 stable image is based in_ [_Distroless_](https://github.com/GoogleContainerTools/distroless) _focusing on security containing just the Fluent Bit binary and minimal system libraries and basic configuration. Optionally, we provide \_debug_ images for x86\_64 which contains Busybox that can be used to troubleshoot or testing purposes.
+Our x86\_64 stable image is based in [Distroless](https://github.com/GoogleContainerTools/distroless) focusing on security containing just the Fluent Bit binary and minimal system libraries and basic configuration. Optionally, we provide **debug** images for x86\_64 which contains Busybox that can be used to troubleshoot or testing purposes.
 
-In addition, the main manifest provides images for arm64v8 and arm32v7 architctectures. From a deployment perspective there is no need to specify an architecture, the container client tool that pulls the image gets the proper layer for the running architecture.
+In addition, the main manifest provides images for arm64v8 and arm32v7 architectures. From a deployment perspective there is no need to specify an architecture, the container client tool that pulls the image gets the proper layer for the running architecture.
 
 For every architecture we build the layers using the following base images:
 
@@ -30,22 +30,22 @@ For every architecture we build the layers using the following base images:
 
 ## Getting Started
 
-Download the last stable image from 1.3 series:
+Download the last stable image from 1.4 series:
 
 ```text
-$ docker pull fluent/fluent-bit:1.3
+$ docker pull fluent/fluent-bit:1.4
 ```
 
 Once the image is in place, now run the following \(useless\) test which makes Fluent Bit measure CPU usage by the container:
 
 ```text
-$ docker run -ti fluent/fluent-bit:1.3 /fluent-bit/bin/fluent-bit -i cpu -o stdout -f 1
+$ docker run -ti fluent/fluent-bit:1.4 /fluent-bit/bin/fluent-bit -i cpu -o stdout -f 1
 ```
 
 That command will let Fluent Bit measure CPU usage every second and flush the results to the standard output, e.g:
 
 ```text
-Fluent-Bit v1.3.x
+Fluent-Bit v1.4.x
 Copyright (C) Treasure Data
 
 [2019/10/01 12:29:02] [ info] [engine] started
@@ -67,5 +67,5 @@ Alpine Linux uses Musl C library instead of Glibc. Musl is not fully compatible
 
 Our Docker containers images are deployed thousands of times per day, we take security and stability very seriously.
 
-The _latest_ tag _most of the time_ points to the latest stable image. When we release a major update to Fluent Bit like for example from v1.2.x to v1.3.0, we don't move _latest_ tag until 2 weeks after the release. That give us extra time to verify with our community that everything works as expected.
+The _latest_ tag _most of the time_ points to the latest stable image. When we release a major update to Fluent Bit like for example from v1.3.x to v1.4.0, we don't move _latest_ tag until 2 weeks after the release. That give us extra time to verify with our community that everything works as expected.
 

installation/kubernetes.md

@@ -1,5 +1,5 @@
 ---
-description: Kubernetes Production Grade
+description: Kubernetes Production Grade Log Processor
 ---
 
 # Kubernetes
@@ -46,20 +46,20 @@ The next step is to create a ConfigMap that will be used by our Fluent Bit Daemo
 $ kubectl create -f https://raw.githubusercontent.com/fluent/fluent-bit-kubernetes-logging/master/output/elasticsearch/fluent-bit-configmap.yaml
 ```
 
-### Note for Kubernetes v1.16
+### Note for Kubernetes < v1.16
 
-Starting from Kubernetes v1.16, DaemonSet resources are not longer served from `extensions/v1beta` . Our current Daemonset Yaml files uses the old `apiVersion`.
+For Kubernetes versions olden than v1.16, the DaemonSet resource is not available on `apps/v1` , the resource is available on `apiVersion: extensions/v1beta1` . Our current Daemonset Yaml files uses the new  `apiVersion`.
 
-If you are using Kubernetes v1.16, grab manually a copy of your Daemonset Yaml file and replace the value of `apiVersion` from:
+If you are using and older Kubernetes, grab manually a copy of your Daemonset Yaml file and replace the value of `apiVersion` from:
 
 ```yaml
-apiVersion: extensions/v1beta1
+apiVersion: apps/v1
 ```
 
 to
 
 ```yaml
-apiVersion: apps/v1
+apiVersion: extensions/v1beta1
 ```
 
 You can read more about this deprecation on Kubernetes v1.14 Changelog here:

installation/linux/debian.md

@@ -1,6 +1,6 @@
 # Debian
 
-Fluent Bit is distributed as **td-agent-bit** package and is available for the latest \(and old\) stable Debian systems: Buster, Stretch and Jessie. This stable Fluent Bit distribution package is maintained by [Treasure Data, Inc](https://www.treasuredata.com).
+Fluent Bit is distributed as **td-agent-bit** package and is available for the latest \(and old\) stable Debian systems: Buster, Stretch and Jessie. 
 
 ## Server GPG key
 

installation/linux/raspbian-raspberry-pi.md

@@ -2,9 +2,9 @@
 
 Fluent Bit is distributed as **td-agent-bit** package and is available for the Raspberry, specifically for [Raspbian](http://raspbian.org) distribution, the following versions are supported:
 
-* Raspbian 10
-* Raspbian 9
-* Raspbian 8
+* Raspbian Buster \(10\)
+* Raspbian Stretch \(9\)
+* Raspbian Jessie \(8\)
 
 ## Server GPG key
 

installation/linux/redhat-centos.md

@@ -32,10 +32,10 @@ Once your repository is configured, run the following command to install it:
 $ yum install td-agent-bit
 ```
 
-Now the following step is to instruct _systemd_ to enable the service:
+Now the following step is to instruct _Systemd_ to enable the service:
 
 ```bash
-$ service td-agent-bit start
+$ sudo service td-agent-bit start
 ```
 
 If you do a status check, you should see a similar output like this:

installation/linux/ubuntu.md

@@ -1,6 +1,6 @@
 # Ubuntu
 
-Fluent Bit is distributed as **td-agent-bit** package and is available for the latest stable Ubuntu system: Xenial Xerus. This stable Fluent Bit distribution package is maintained by [Treasure Data, Inc](https://www.treasuredata.com).
+Fluent Bit is distributed as **td-agent-bit** package and is available for the latest stable Ubuntu system: Focal Fossa.
 
 ## Server GPG key
 
@@ -14,6 +14,12 @@ $ wget -qO - https://packages.fluentbit.io/fluentbit.key | sudo apt-key add -
 
 On Ubuntu, you need to add our APT server entry to your sources lists, please add the following content at bottom of your **/etc/apt/sources.list** file:
 
+#### Ubuntu 20.04 LTS \(Focal Fossa\)
+
+```text
+deb https://packages.fluentbit.io/ubuntu/focal focal main
+```
+
 #### Ubuntu 18.04 LTS \(Bionic Beaver\)
 
 ```text

installation/windows.md

@@ -4,19 +4,19 @@ Fluent Bit is distributed as **td-agent-bit** package for Windows. Fluent Bit ha
 
 ## Installation Packages
 
-The latest stable version is 1.2.2.
+The latest stable version is 1.4.0.
 
 | INSTALLERS | SHA256 CHECKSUMS |
 | :--- | :--- |
-| td-agent-bit-1.2.2-win32.exe | b9e2695e6cc1b15e0e47d20624d6509cecbdd1767b6681751190f54e52832b6a |
-| td-agent-bit-1.2.2-win32.zip | 4212e28fb6cb970ce9f27439f8dce3281ab544a4f7c9ae71991480a7e7a64afd |
-| td-agent-bit-1.2.2-win64.exe | 6059e2f4892031125aac30325be4c167daed89742705fa883d34d91dc306645e |
-| td-agent-bit-1.2.2-win64.zip | a6a02e7027f4409c1392e6df0c1463d5e979deab818f23959b4a00c741399e8e |
+| td-agent-bit-1.4.0-win32.exe |  |
+| td-agent-bit-1.4.0-win32.zip |  |
+| td-agent-bit-1.4.0-win64.exe |  |
+| td-agent-bit-1.4.0-win64.zip |  |
 
 To check the integrity, use `Get-FileHash` commandlet on PowerShell.
 
 ```text
-PS> Get-FileHash td-agent-bit-1.2.2-win32.exe
+PS> Get-FileHash td-agent-bit-1.4.0-win32.exe
 ```
 
 ## Installing from ZIP archive
@@ -26,7 +26,7 @@ Download a ZIP archive [from the download page](https://fluentbit.io/). There ar
 Then you need to expand the ZIP archive. You can do this by clicking "Extract All" on Explorer, or if you're using PowerShell, you can use `Expand-Archive` commandlet.
 
 ```text
-PS> Expand-Archive td-agent-bit-1.2.0-win64.zip
+PS> Expand-Archive td-agent-bit-1.4.0-win64.zip
 ```
 
 The ZIP package contains the following set of files.
@@ -57,8 +57,11 @@ If you see the following output, it's working fine!
 
 ```text
 PS> .\bin\fluent-bit.exe  -i dummy -o stdout
-Fluent Bit v1.2.0
-Copyright (C) Treasure Data
+Fluent Bit v1.4.0
+* Copyright (C) 2019-2020 The Fluent Bit Authors
+* Copyright (C) 2015-2018 Treasure Data
+* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
+* https://fluentbit.io
 
 [2019/06/28 10:13:04] [ info] [storage] initializing...
 [2019/06/28 10:13:04] [ info] [storage] in-memory
@@ -79,7 +82,7 @@ Download an EXE installer from the [download page](https://fluentbit.io/download
 
 Then, double-click the EXE installer you've downloaded. Installation wizard will automatically start.
 
-![](https://github.com/fluent/fluent-bit-docs/tree/8ab2f4cda8dfdd8def7fa0cf5c7ffc23069e5a70/imgs/windows_installer.png)
+![](../.gitbook/assets/windows_installer%20%281%29.png)
 
 Click Next and proceed. By default, Fluent Bit is installed into `C:\Program Files\td-agent-bit\`, so you should be able to launch fluent-bit as follow after installation.
 

installation/yocto-embedded-linux.md

@@ -7,11 +7,11 @@ We distribute two main recipes, one for testing/dev purposes and other with the
 | Version | Recipe | Description |
 | :--- | :--- | :--- |
 | devel | [fluent-bit\_git.bb](https://github.com/fluent/fluent-bit/blob/master/fluent-bit_git.bb) | Build Fluent Bit from GIT master. This recipe aims to be used for development and testing purposes only. |
-| v1.2.0 | [fluent-bit\_1.2.0.bb](https://github.com/fluent/fluent-bit/blob/1.2/fluent-bit_1.2.0.bb) | Build latest stable version of Fluent Bit. |
+| v1.4.0 | [fluent-bit\_1.4.0.bb](https://github.com/fluent/fluent-bit/blob/master/fluent-bit_1.4.0.bb) | Build latest stable version of Fluent Bit. |
 
 It's strongly recommended to always use the stable release of Fluent Bit recipe and not the one from GIT master for production deployments.
 
-## Fluent Bit v1.1 and native ARMv8 \(aarch64\) support
+## Fluent Bit and other architectures
 
-Fluent Bit >= v1.1.x already integrates native AArch64 support where stack switches for co-routines are done through native ASM calls, on this scenario there is no issues as the one faced in previous series.
+Fluent Bit >= v1.1.x fully supports x86\_64, x86, arm32v7 and arm64v8.