Fluent Bit source plugin

The Fluent Bit source plugin lets you ingest data from your Fluent Bit instances into Chronosphere Telemetry Pipeline.

Supported telemetry types

This plugin supports these telemetry types:

Logs	Metrics	Traces

Configuration parameters

Use the parameters in this section to configure your plugin. The Telemetry Pipeline web interface uses the values in the Name column to describe the parameters. Items in the Key column are the YAML keys to use in pipeline configuration files.

General

Name	Key	Description	Default
Port	`port`	Required. The TCP port listening for incoming messages.	none

Security and TLS

Name	Key	Description	Default
TLS	`tls`	Enable or disable TLS/SSL support. Accepted values: `true`, `false`.	`false`
TLS Certificate Validation	`tls.verify`	Enable or disable TLS/SSL certificate validation. TLS must be enabled for certificates to be validated. Accepted values: `off`, `on`.	`on`
TLS Debug Level	`tls.debug`	Set TLS debug verbosity level. Accepted values: `0` (No debug), `1` (Error), `2` (State change), `3` (Informational), `4` (Verbose).	`1`
CA Certificate File Path	`tls.ca_file`	Absolute path to CA certificate file.	none
Certificate File Path	`tls.crt_file`	Absolute path to certificate file.	none
Private Key File Path	`tls.key_file`	Absolute path to private key file.	none
Private Key Path Password	`tls.key_passwd`	Password for private key file.	none
TLS SNI Hostname Extension	`tls.vhost`	Hostname to be used for TLS SNI extension.	none

Configuring Fluent Bit to route data to Telemetry Pipeline

You can use the out_forward Fluent Bit plugin to route data to the Fluent Bit data source in Chronosphere Telemetry Pipeline. In your Fluent Bit configuration, use the following configuration:

[OUTPUT]
    Name          forward
    Match         *
    Host          127.0.0.1
    Port          24244

Elasticsearch HTTP Fluentd