The Systemd input plugin allows to collect log messages from the Journald daemon on Linux environments.
The plugin supports the following configuration parameters:
Optional path to the Systemd journal directory, if not set, the plugin will use default paths to read local-only logs.
Set a maximum number of fields (keys) allowed per record.
When Fluent Bit starts, the Journal might have a high number of logs in the queue. In order to avoid delays and reduce memory usage, this option allows to specify the maximum number of log entries that can be processed per round. Once the limit is reached, Fluent Bit will continue processing the remaining log entries once Journald performs the notification.
allows to perform a query over logs that contains a specific Journald key/value pairs, e.g: _SYSTEMD_UNIT=UNIT. The Systemd_Filter option can be specified multiple times in the input section to apply multiple filters as required.
The tag is used to route messages but on Systemd plugin there is an extra functionality: if the tag includes a star/wildcard, it will be expanded with the Systemd Unit file (e.g: host.* => host.UNIT_NAME).
Specify the absolute path of a database file to keep track of Journald cursor.
Start reading new entries. skip entries already stored in Journald.
In order to receive Systemd messages, you can run the plugin from the command line or through the configuration file:
From the command line you can let Fluent Bit listen for Systemd messages with the following options:
$ fluent-bit -i systemd \-p systemd_filter=_SYSTEMD_UNIT=docker.service \-p tag='host.*' -o stdout
In the example above we are collecting all messages coming from the Docker service.
In your main configuration file append the following Input & Output sections:
[SERVICE]Flush 1Log_Level infoParsers_File parsers.conf[INPUT]Name systemdTag host.*Systemd_Filter _SYSTEMD_UNIT=docker.service[OUTPUT]Name stdoutMatch *