For production systems, we strongly suggest that you always get the latest stable release of the source code in either zip or tarball format from Github using the following link pattern:
https://github.com/fluent/fluent-bit/archive/refs/tags/v<release version>.tar.gz https://github.com/fluent/fluent-bit/archive/refs/tags/v<release version>.zip
For example for version 1.8.12 the link is the following: https://github.com/fluent/fluent-bit/archive/refs/tags/v1.8.12.tar.gz
For anyone who aims to contribute to the project by testing or extending the code base, you can get the development version from our GIT repository:
Note that our master branch is where the development of Fluent Bit happens. Since it's a development version, expect issues when compiling or at run time.
We encourage everybody to help us testing every development version, at the end this is what will become stable.
uses as it build system. The suggested procedure to prepare the build system consists of the following steps:
In the following steps you can find exact commands to build and install the project with the default options. If you already know how CMake works you can skip this part and look at the build options available. Note that Fluent Bit requires CMake 3.x. You may need to use
cmake3
instead ofcmake
to complete the following steps on your system.
Change to the build/ directory inside the Fluent Bit sources:
Let configure the project specifying where the root path is located:
Now you are ready to start the compilation process through the simple make command:
to continue installing the binary on the system just do:
it's likely you may need root privileges so you can try to prefixing the command with sudo.
Fluent Bit provides certain options to CMake that can be enabled or disabled when configuring, please refer to the following tables under the General Options, Development Options, Input Plugins and _Output Plugins sections.
The input plugins provides certain features to gather information from a specific source type which can be a network interface, some built-in metric or through a specific input device, the following input plugins are available:
The filter plugins allows to modify, enrich or drop records. The following table describes the filters available on this version:
The output plugins gives the capacity to flush the information to some external interface, service or terminal, the following table describes the output plugins available as of this version:
option | description | default |
---|
option | description | default |
---|
option | description | default |
---|
option | description | default |
---|
option | description | default |
---|
FLB_ALL | Enable all features available | No |
FLB_JEMALLOC | Use Jemalloc as default memory allocator | No |
FLB_TLS | Build with SSL/TLS support | Yes |
FLB_BINARY | Build executable | Yes |
FLB_EXAMPLES | Build examples | Yes |
FLB_SHARED_LIB | Build shared library | Yes |
FLB_MTRACE | Enable mtrace support | No |
FLB_INOTIFY | Enable Inotify support | Yes |
FLB_POSIX_TLS | Force POSIX thread storage | No |
FLB_SQLDB | Enable SQL embedded database support | No |
FLB_HTTP_SERVER | Enable HTTP Server | No |
FLB_LUAJIT | Enable Lua scripting support | Yes |
FLB_RECORD_ACCESSOR | Enable record accessor | Yes |
FLB_SIGNV4 | Enable AWS Signv4 support | Yes |
FLB_STATIC_CONF | Build binary using static configuration files. The value of this option must be a directory containing configuration files. |
FLB_STREAM_PROCESSOR | Enable Stream Processor | Yes |
FLB_DEBUG | Build binaries with debug symbols | No |
FLB_VALGRIND | Enable Valgrind support | No |
FLB_TRACE | Enable trace mode | No |
FLB_SMALL | Minimise binary size | No |
FLB_TESTS_RUNTIME | Enable runtime tests | No |
FLB_TESTS_INTERNAL | Enable internal tests | No |
FLB_TESTS | Enable tests | No |
FLB_BACKTRACE | Enable backtrace/stacktrace support | Yes |
Fluent Bit in normal operation mode allows to be configurable through text files or using specific arguments in the command line, while this is the ideal deployment case, there are scenarios where a more restricted configuration is required: static configuration mode.
Static configuration mode aims to include a built-in configuration in the final binary of Fluent Bit, disabling the usage of external files or flags at runtime.
The following steps assumes you are familiar with configuring Fluent Bit using text files and you have experience building it from scratch as described in the Build and Install section.
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. It is mandatory that this directory contain as a minimum one configuration file called fluent-bit.conf containing the required SERVICE, INPUT and OUTPUT sections. As an example create a new fluent-bit.conf file with the following content:
the configuration provided above will calculate CPU metrics from the running system and print them to the standard output interface.
Inside Fluent Bit source code, get into the build/ directory and run CMake appending the FLB_STATIC_CONF option pointing the configuration directory recently created, e.g:
then build it:
At this point the fluent-bit binary generated is ready to run without necessity of further configuration:
Enable Collectd input plugin | On |
Enable CPU input plugin | On |
Enable Disk I/O Metrics input plugin | On |
Enable Docker metrics input plugin | On |
Enable Exec input plugin | On |
Enable Forward input plugin | On |
Enable Head input plugin | On |
Enable Health input plugin | On |
Enable Kernel log input plugin | On |
Enable Memory input plugin | On |
Enable MQTT Server input plugin | On |
Enable Network I/O metrics input plugin | On |
Enable Process monitoring input plugin | On |
Enable Random input plugin | On |
Enable Serial input plugin | On |
Enable Standard input plugin | On |
Enable Syslog input plugin | On |
Enable Systemd / Journald input plugin | On |
Enable Tail (follow files) input plugin | On |
Enable TCP input plugin | On |
Enable system temperature(s) input plugin | On |
Enable Windows Event Log input plugin (Windows Only) | On |
Enable AWS metadata filter | On |
FLB_FILTER_EXPECT | Enable Expect data test filter | On |
Enable Grep filter | On |
Enable Kubernetes metadata filter | On |
Enable Lua scripting filter | On |
Enable Modify filter | On |
Enable Nest filter | On |
Enable Parser filter | On |
Enable Record Modifier filter | On |
Enable Rewrite Tag filter | On |
Enable Stdout filter | On |
Enable Throttle filter | On |
Enable Microsoft Azure output plugin | On |
Enable Google BigQuery output plugin | On |
Enable Counter output plugin | On |
Enable Amazon CloudWatch output plugin | On |
Enable Datadog output plugin | On |
On |
Enable File output plugin | On |
Enable Amazon Kinesis Data Firehose output plugin | On |
Enable Amazon Kinesis Data Streams output plugin | On |
Enable Flowcounter output plugin | On |
On |
Enable Gelf output plugin | On |
Enable HTTP output plugin | On |
Enable InfluxDB output plugin | On |
Enable Kafka output | Off |
Enable Kafka REST Proxy output plugin | On |
FLB_OUT_LIB | Enable Lib output plugin | On |
On |
FLB_OUT_NULL | Enable NULL output plugin | On |
FLB_OUT_PGSQL | Enable PostgreSQL output plugin | On |
FLB_OUT_PLOT | Enable Plot output plugin | On |
FLB_OUT_SLACK | Enable Slack output plugin | On |
Enable Amazon S3 output plugin | On |
Enable Splunk output plugin | On |
Enable Google Stackdriver output plugin | On |
Enable STDOUT output plugin | On |
FLB_OUT_TCP | Enable TCP/TLS output plugin | On |
On |
Enable output plugin
Enable output plugin
Enable output plugin
Enable output plugin