Skip to main content
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:
LogsMetricsTraces

​
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

NameKeyDescriptionDefault
PortportRequired. The TCP port listening for incoming messages.none

​
Security and TLS

NameKeyDescriptionDefault
TLStlsIf true, enables TLS/SSL. If false, disables TLS/SSL. Accepted values: true, false.false
TLS Certificate Validationtls.verifyIf 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 Leveltls.debugSets TLS debug verbosity level. Accepted values: 0 (No debug), 1 (Error), 2 (State change), 3 (Informational), 4 (Verbose).1
CA Certificate File Pathtls.ca_fileAbsolute path to CA certificate file.none
Certificate File Pathtls.crt_fileAbsolute path to certificate file.none
Private Key File Pathtls.key_fileAbsolute path to private key file.none
Private Key Path Passwordtls.key_passwdPassword for private key file.none
TLS SNI Hostname Extensiontls.vhostHostname to be used for TLS SNI extension.none

​
Advanced

NameKeyDescriptionDefault
Memory Buffer Limitmem_buf_limitFor pipelines with the Deployment or DaemonSet workload type only. 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.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