Fluent Bit source plugin - Chronosphere Documentation

This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.

The Fluent Bit source plugin (name: forward, alias: Fluent_Bit) lets you ingest data from your Fluent Bit instances into a telemetry pipeline. This is a push-based source plugin.

Supported telemetry types

The for Chronosphere Telemetry Pipeline supports these telemetry types:

Logs	Metrics	Traces

Configuration parameters

Use the parameters in this section to configure the . The Telemetry Pipeline web interface uses the items in the Name column to describe these parameters. Pipeline configuration files use the items in the Key column as YAML keys.

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`	If `true`, enables TLS/SSL. If `false`, disables TLS/SSL. Accepted values: `true`, `false`.	`false`
TLS Certificate Validation	`tls.verify`	If `on`, and if `tls` is `true`, enables TLS/SSL certificate validation. If `off`, disables TLS/SSL certificate validation. Accepted values: `on`, `off`.	`on`
TLS Debug Level	`tls.debug`	Sets 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

Advanced

Name	Key	Description	Default
Memory Buffer Limit	`mem_buf_limit`	Sets a limit for how much buffered data the plugin can write to memory, which affects backpressure. This value must follow Fluent Bit’s rules for unit sizes. If unspecified, no limit is enforced. For v2 pipelines, this parameter affects only pipelines with the Deployment or DaemonSet workload type. To learn more, see the v2 backpressure guide. For v3 pipelines, this parameter is independent from the OpenTelemetry `memory_limiter` and `batch` processors.	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

​Supported telemetry types

​Configuration parameters

​General

​Security and TLS

​Advanced

​Configuring Fluent Bit to route data to Telemetry Pipeline

Supported telemetry types

Configuration parameters

General

Security and TLS

Advanced

Configuring Fluent Bit to route data to Telemetry Pipeline