Skip to main content
Version: v4.24

fluent-bit

Sends and receives events via Fluent Bit.

Synopsis​

fluent-bit [-X|--set <key=value>,...] <plugin> [<key=value>...]

Description​

The fluent-bit operator acts as a bridge into the Fluent Bit ecosystem, making it possible to acquire events from a Fluent Bit input plugin and process events with a Fluent Bit output plugin.

Syntactically, the fluent-bit operator behaves similar to an invocation of the fluent-bit command line utility. For example, the invocation

fluent-bit -o plugin -p key1=value1 -p key2=value2 -p ...

translates to our fluent-bit operator as follows:

fluent-bit plugin key1=value1 key2=value2 ...

-X|--set <key=value>​

A comma-separated list of key-value pairs that represent the global properties of the Fluent Bit service., e.g., -X flush=1,grace=3.

Consult the list of available key-value pairs to configure Fluent Bit according to your needs.

We recommend factoring these options into the plugin-specific fluent-bit.yaml so that they are independent of the fluent-bit operator arguments.

<plugin>​

The name of the Fluent Bit plugin.

Run fluent-bit -h and look under the Inputs and Outputs section of the help text for available plugin names. The web documentation often comes with an example invocation near the bottom of the page, which also provides a good idea how you could use the operator.

<key=value>​

Sets a plugin configuration property.

The positional arguments of the form key=value are equivalent to the multi-option -p key=value of the fluent-bit executable.

Examples​

Source​

Ingest OpenTelemetry logs, metrics, and traces:

fluent-bit opentelemetry

You can then send JSON-encoded log data to a freshly created API endpoint:

curl \
  --header "Content-Type: application/json" \
  --request POST \
  --data '{"resourceLogs":[{"resource":{},"scopeLogs":[{"scope":{},"logRecords":[{"timeUnixNano":"1660296023390371588","body":{"stringValue":"{\"message\":\"dummy\"}"},"traceId":"","spanId":""}]}]}]}' \
  http://0.0.0.0:4318/v1/logs

Handle Splunk HTTP HEC requests:

fluent-bit splunk port=8088

Handle ElasticSearch & OpenSearch Bulk API requests or ingest from beats (e.g., Filebeat, Metricbeat, Winlogbeat):

fluent-bit elasticsearch port=9200

Sink​

Send events to Slack:

fluent-bit slack webhook=https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX

Send events to Splunk:

fluent-bit splunk host=127.0.0.1 port=8088 tls=on tls.verify=off splunk_token=11111111-2222-3333-4444-555555555555

Send events to ElasticSearch:

fluent-bit es host=192.168.2.3 port=9200 index=my_index type=my_type