Redhat / CentOS
Last updated
Was this helpful?
Last updated
Was this helpful?
Fluent Bit is distributed as the fluent-bit package and is available for the latest
stable CentOS system.
Fluent Bit supports the following architectures:
x86_64
aarch64
arm64v8
For CentOS 9 and later, Fluent Bit uses as the canonical base system.
Fluent Bit provides an installation script to use for most Linux targets. This will always install the most recently released version.
This is a convenience helper and should always be validated prior to use. The recommended secure deployment approach is to use the following instructions:
CentOS 8 is now end-of-life, so the default Yum repositories are unavailable.
Ensure you've configured an appropriate mirror. For example:
An alternative is to use Rocky or Alma Linux, which should be equivalent.
The fluent-bit is provided through a Yum repository. To add the repository
reference to your system:
In /etc/yum.repos.d/, add a new file called fluent-bit.repo.
Add the following content to the file:
As a best practice, enable gpgcheck and repo_gpgcheck for security reasons.
Fluent Bit signs its repository metadata and all Fluent Bit packages.
The GPG Key fingerprint of the new key is:
The GPG Key fingerprint of the old key is:
After your repository is configured, run the following command to install it:
Instruct Systemd to enable the service:
If you do a status check, you should see a similar output like this:
The default Fluent Bit configuration collect metrics of CPU usage and sends the
records to the standard output. You can see the outgoing data in your/var/log/messages file.
The fluent-bit.repo file for the latest installations of Fluent Bit uses a$releasever variable to determine the correct version of the package to install to
your system:
Depending on your Red Hat distribution version, this variable can return a value
other than the OS major release version (for example, RHEL7 Server distributions return7Server instead of 7). The Fluent Bit package URL uses the major OS
release version, so any other value here will cause a 404.
To resolve this issue, replace the $releasever variable with your system's OS major
release version. For example:
For the 1.9.0 and 1.8.15 and later releases, the. Ensure this new one is added.
The previous key is and might be required to install previous versions.
Refer to the to see which platforms are supported in each release.