Build and Install
Fluent Bit uses CMake as its build system.
Requirements
CMake 3.12 or greater. You might need to use
cmake3
instead ofcmake
.Flex
Bison 3 or greater
YAML headers
OpenSSL headers
Prepare environment
If you already know how CMake works, you can skip this section and review the available build options.
The following steps explain how to build and install the project with the default options.
Change to the
build/
directory inside the Fluent Bit sources:Let CMake configure the project specifying where the root path is located:
This command displays a series of results similar to:
Start the compilation process using the
make
command:This command displays results similar to:
To continue installing the binary on the system, use
make install
:If the command indicates insufficient permissions, prefix the command with
sudo
.
Build options
Fluent Bit provides configurable options to CMake that can be enabled or disabled.
General options
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_CONFIG_YAML
Enable YAML configuration support
Yes
FLB_WASM
Build with WASM runtime support
Yes
FLB_WAMRC
Build with WASM AOT compiler executable
No
Development options
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
Optimization options
FLB_MSGPACK_TO_JSON_INIT_BUFFER_SIZE
Determine initial buffer size for msgpack
to json
conversion in terms of memory used by payload.
2.0
FLB_MSGPACK_TO_JSON_REALLOC_BUFFER_SIZE
Determine percentage of reallocation size when msgpack
to json
conversion buffer runs out of memory.
0.1
Input plugins
Input plugins gather information from a specific source type like network interfaces, some built-in metrics, or through a specific input device. The following input plugins are available:
Filter plugins
Filter plugins let you modify, enrich or drop records. The following table describes the filters available on this version:
FLB_FILTER_EXPECT
Enable Expect data test filter
On
Output plugins
Output plugins let you flush the information to some external interface, service, or terminal. The following table describes the output plugins available:
FLB_OUT_LIB
Enable Lib output plugin
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
FLB_OUT_TCP
Enable TCP/TLS output plugin
On
Processor plugins
Processor plugins handle the events within the processor pipelines to allow modifying, enriching, or dropping events.
The following table describes the processors available:
| Option | Description | Default || :--- | :--- | :--- | | FLB_PROCESSOR_METRICS_SELECTOR
| Enable metrics selector processor | On | | FLB_PROCESSOR_LABELS
| Enable metrics label manipulation processor | On |
Last updated