Connect Fluent Bit to Bronto

Use the following single line command to configure the Fluent Bit repository and install the Fluent Bit log collector.

curl https://raw.githubusercontent.com/fluent/fluent-bit/master/install.sh | sh

Manual instructions

Add Server GPG Key

sudo apt update
sudo apt install ca-certificates curl gnupg
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://packages.fluentbit.io/fluentbit.key | sudo gpg --dearmor -o /etc/apt/keyrings/fluentbit.gpg
sudo chmod a+r /etc/apt/keyrings/fluentbit.gpg

Add Repo

In order to download the latest version of Fluent Bit, add the Fluent Bit repository to your source list.

echo  "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/fluentbit.gpg] https://packages.fluentbit.io/ubuntu/"$(. /etc/os-release && echo "$VERSION_CODENAME")"  "$(. /etc/os-release && echo "$VERSION_CODENAME")" main" |  sudo tee /etc/apt/sources.list.d/fluentbit.list > /dev/null

Install Package

Install the Fluent Bit from the repository setup in the previous step

sudo apt update
sudo apt install fluent-bit

Configure Fluent Bit

After installation, Fluent Bit requires an output configuration to communicate with the Bronto system.

/opt/homebrew/etc/fluent-bit.conf

[SERVICE]
    flush           10
    daemon          off
    log_level       info

[INPUT]
    name            tail
    path            /path/to/your/logs
    tag             <OPTIONAL_LOG_TAG>
    refresh_interval 5
    mem_buf_limit   5MB
    skip_long_lines on

[OUTPUT]
    name            http
    tls             on
    match           *
    host            ingestion.<REGION>.bronto.io
    port            443
    format          json_lines
    compress        gzip
    header          x-bronto-api-key <YOUR_API_KEY>
    header          x-bronto-service-name <YOUR_SERVICE_NAME>
    header          x-bronto-service-name-namespace <YOUR_SERVICE_NAMESPACE>
    header          x-bronto-tags: <key1=value1,key2=value2>

Parameter	Value	Requirement	Description
name	HTTP	Required	Specifies the output plugin used by Fluent Bit.
tls	on	Required	Enables the use of TLS for secure communication.
host	ingestion<REGION>.bronto.io	Required	The Bronto endpoint responsible for ingesting log data. Supported regions: EU & US.
port	443	Required	Specifies the network port for communication.
format	json_lines or msgpack	Required	Specify the data format to be used in the HTTP request body, by default it uses msgpack.
compress	gzip	Optional	Recommended. Compresses the payload in GZIP format. Bronto supports and recommends using gzip for efficient data transmission.
header (x-bronto-service-name)	Your Service Name	Required	Specifies the name of the service.
header (x-bronto-service-namespace)	Your Service Namespace	Optional	Specifies the namespace for organizational purposes.
header (x-bronto-tags)	Tags	Optional	Specifies the tags to apply to logs. A tag is a key-value pair applied to a log to hold metadata about that log. Each tag is a label consisting of a key and a required value.

The table below lists the parameters used to determine the Bronto dataset associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-name	HTTP Header
x-bronto-log-name	HTTP Header
kubernetes.annotations.logs.bronto.io/dataset	Log Metadata
service.name	Log Metadata
service_name	Log Metadata
kubernetes.annotations.service_name	Log Metadata
kubernetes.labels.app.kubernetes.io/name	Log Metadata
kubernetes.container_name	Log Metadata

The table below lists the parameters used to determine the Bronto collection associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-namespace	HTTP Header
x-bronto-logset	HTTP Header
kubernetes.annotations.logs.bronto.io/collection	Log Metadata
service.namespace	Log Metadata
service_namespace	Log Metadata

Finally the table below lists the parameters used to assign tags to datasets, ordered from highest to lowest precedence.

Parameter Name	Parameter Type	Example
x-bronto-tags	HTTP Header	x-bronto-tags: tag1=value1,tag2=value2,…
kubernetes.annotations.tags.logs.bronto.io/<TAG_NAME>	Log Metadata	kubernetes.annotations.tags.logs.bronto.io/tag1: value1

Verify Log Collection

Once you have applied your configuration and restarted Fluent Bit, you can expect to see your log data being ingested to Bronto and accessible via the Search page.

Use the following single line command to configure the Fluent Bit repository and install the Fluent Bit log collector.

curl https://raw.githubusercontent.com/fluent/fluent-bit/master/install.sh | sh

Manual instructions

Add Server GPG Key

sudo apt update
sudo apt install ca-certificates curl gnupg
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://packages.fluentbit.io/fluentbit.key | sudo gpg --dearmor -o /etc/apt/keyrings/fluentbit.gpg
sudo chmod a+r /etc/apt/keyrings/fluentbit.gpg

Add Repo

In order to download the latest version of Fluent Bit, add the Fluent Bit repository to your source list.

echo  "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/fluentbit.gpg] https://packages.fluentbit.io/ubuntu/"$(. /etc/os-release && echo "$VERSION_CODENAME")"  "$(. /etc/os-release && echo "$VERSION_CODENAME")" main" |  sudo tee /etc/apt/sources.list.d/fluentbit.list > /dev/null

Install Package

Install the Fluent Bit from the repository setup in the previous step

sudo apt update
sudo apt install fluent-bit

Configure Fluent Bit

After installation, Fluent Bit requires an output configuration to communicate with the Bronto system.

/opt/homebrew/etc/fluent-bit.conf

[SERVICE]
    flush           10
    daemon          off
    log_level       info

[INPUT]
    name            tail
    path            /path/to/your/logs
    tag             <OPTIONAL_LOG_TAG>
    refresh_interval 5
    mem_buf_limit   5MB
    skip_long_lines on

[OUTPUT]
    name            http
    tls             on
    match           *
    host            ingestion.<REGION>.bronto.io
    port            443
    format          json_lines
    compress        gzip
    header          x-bronto-api-key <YOUR_API_KEY>
    header          x-bronto-service-name <YOUR_SERVICE_NAME>
    header          x-bronto-service-name-namespace <YOUR_SERVICE_NAMESPACE>
    header          x-bronto-tags: <key1=value1,key2=value2>

Parameter	Value	Requirement	Description
name	HTTP	Required	Specifies the output plugin used by Fluent Bit.
tls	on	Required	Enables the use of TLS for secure communication.
host	ingestion<REGION>.bronto.io	Required	The Bronto endpoint responsible for ingesting log data. Supported regions: EU & US.
port	443	Required	Specifies the network port for communication.
format	json_lines or msgpack	Required	Specify the data format to be used in the HTTP request body, by default it uses msgpack.
compress	gzip	Optional	Recommended. Compresses the payload in GZIP format. Bronto supports and recommends using gzip for efficient data transmission.
header (x-bronto-service-name)	Your Service Name	Required	Specifies the name of the service.
header (x-bronto-service-namespace)	Your Service Namespace	Optional	Specifies the namespace for organizational purposes.
header (x-bronto-tags)	Tags	Optional	Specifies the tags to apply to logs. A tag is a key-value pair applied to a log to hold metadata about that log. Each tag is a label consisting of a key and a required value.

The table below lists the parameters used to determine the Bronto dataset associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-name	HTTP Header
x-bronto-log-name	HTTP Header
kubernetes.annotations.logs.bronto.io/dataset	Log Metadata
service.name	Log Metadata
service_name	Log Metadata
kubernetes.annotations.service_name	Log Metadata
kubernetes.labels.app.kubernetes.io/name	Log Metadata
kubernetes.container_name	Log Metadata

The table below lists the parameters used to determine the Bronto collection associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-namespace	HTTP Header
x-bronto-logset	HTTP Header
kubernetes.annotations.logs.bronto.io/collection	Log Metadata
service.namespace	Log Metadata
service_namespace	Log Metadata

Finally the table below lists the parameters used to assign tags to datasets, ordered from highest to lowest precedence.

Parameter Name	Parameter Type	Example
x-bronto-tags	HTTP Header	x-bronto-tags: tag1=value1,tag2=value2,…
kubernetes.annotations.tags.logs.bronto.io/<TAG_NAME>	Log Metadata	kubernetes.annotations.tags.logs.bronto.io/tag1: value1

Verify Log Collection

Once you have applied your configuration and restarted Fluent Bit, you can expect to see your log data being ingested to Bronto and accessible via the Search page.

Use the following single line command to configure the Fluent Bit repository and install the Fluent Bit log collector.

curl https://raw.githubusercontent.com/fluent/fluent-bit/master/install.sh | sh

Manual instructions

Add Repo

In order to download the latest version of Fluent Bit, add the Fluent Bit repository to your yum repo list.

echo -e \
"[fluent-bit]\n"\
"name = Fluent Bit\n"\
"baseurl = https://packages.fluentbit.io/centos/$(rpm -q --queryformat '%{VERSION}' centos-release)/\n"\
"gpgcheck=1\n"\
"gpgkey=https://packages.fluentbit.io/fluentbit.key\n"\
"repo_gpgcheck=1\n"\
"enabled=1\n" | \
sudo tee /etc/yum.repos.d/fluent-bit.repo > /dev/null

Install Package

Install the Fluent Bit from the repository setup in the previous step.

sudo yum install fluent-bit

Configure Fluent Bit

After installation, Fluent Bit requires an output configuration to communicate with the Bronto system.

[SERVICE]
    flush           10
    daemon          off
    log_level       info

[INPUT]
    name            tail
    path            /path/to/your/logs
    tag             <OPTIONAL_LOG_TAG>
    refresh_interval 5
    mem_buf_limit   5MB
    skip_long_lines on

[OUTPUT]
    name            http
    tls             on
    match           *
    host            ingestion.<REGION>.bronto.io
    port            443
    format          json_lines
    compress        gzip
    header          x-bronto-api-key <YOUR_API_KEY>
    header          x-bronto-service-name <YOUR_SERVICE_NAME>
    header          x-bronto-service-name-namespace <YOUR_SERVICE_NAMESPACE>
    header          x-bronto-tags: <key1=value1,key2=value2>

Parameter	Value	Requirement	Description
name	HTTP	Required	Specifies the output plugin used by Fluent Bit.
tls	on	Required	Enables the use of TLS for secure communication.
host	ingestion<REGION>.bronto.io	Required	The Bronto endpoint responsible for ingesting log data. Supported regions: EU & US.
port	443	Required	Specifies the network port for communication.
format	json_lines or msgpack	Required	Specify the data format to be used in the HTTP request body, by default it uses msgpack.
compress	gzip	Optional	Recommended. Compresses the payload in GZIP format. Bronto supports and recommends using gzip for efficient data transmission.
header (x-bronto-service-name)	Your Service Name	Required	Specifies the name of the service.
header (x-bronto-service-namespace)	Your Service Namespace	Optional	Specifies the namespace for organizational purposes.
header (x-bronto-tags)	Tags	Optional	Specifies the tags to apply to logs. A tag is a key-value pair applied to a log to hold metadata about that log. Each tag is a label consisting of a key and a required value.

The table below lists the parameters used to determine the Bronto dataset associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-name	HTTP Header
x-bronto-log-name	HTTP Header
kubernetes.annotations.logs.bronto.io/dataset	Log Metadata
service.name	Log Metadata
service_name	Log Metadata
kubernetes.annotations.service_name	Log Metadata
kubernetes.labels.app.kubernetes.io/name	Log Metadata
kubernetes.container_name	Log Metadata

The table below lists the parameters used to determine the Bronto collection associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-namespace	HTTP Header
x-bronto-logset	HTTP Header
kubernetes.annotations.logs.bronto.io/collection	Log Metadata
service.namespace	Log Metadata
service_namespace	Log Metadata

Finally the table below lists the parameters used to assign tags to datasets, ordered from highest to lowest precedence.

Parameter Name	Parameter Type	Example
x-bronto-tags	HTTP Header	x-bronto-tags: tag1=value1,tag2=value2,…
kubernetes.annotations.tags.logs.bronto.io/<TAG_NAME>	Log Metadata	kubernetes.annotations.tags.logs.bronto.io/tag1: value1

Verify Log Collection

Once you have applied your configuration and restarted Fluent Bit, you can expect to see your log data being ingested to Bronto and accessible via the Search page.

To retrieve the latest Fluent Bit docker image use the following command.

docker pull fluent/fluent-bit:latest

Configure Fluent Bit

After installation, Fluent Bit requires an output configuration to communicate with the Bronto system.

[SERVICE]
    flush           10
    daemon          off
    log_level       info

[INPUT]
    name            tail
    path            /path/to/your/logs
    tag             <OPTIONAL_LOG_TAG>
    refresh_interval 5
    mem_buf_limit   5MB
    skip_long_lines on

[OUTPUT]
    name            http
    tls             on
    match           *
    host            ingestion.<REGION>.bronto.io
    port            443
    format          json_lines
    compress        gzip
    header          x-bronto-api-key <YOUR_API_KEY>
    header          x-bronto-service-name <YOUR_SERVICE_NAME>
    header          x-bronto-service-name-namespace <YOUR_SERVICE_NAMESPACE>
    header          x-bronto-tags: <key1=value1,key2=value2>
    

Parameter	Value	Requirement	Description
name	HTTP	Required	Specifies the output plugin used by Fluent Bit.
tls	on	Required	Enables the use of TLS for secure communication.
host	ingestion<REGION>.bronto.io	Required	The Bronto endpoint responsible for ingesting log data. Supported regions: EU & US.
port	443	Required	Specifies the network port for communication.
format	json_lines or msgpack	Required	Specify the data format to be used in the HTTP request body, by default it uses msgpack.
compress	gzip	Optional	Recommended. Compresses the payload in GZIP format. Bronto supports and recommends using gzip for efficient data transmission.
header (x-bronto-service-name)	Your Service Name	Required	Specifies the name of the service.
header (x-bronto-service-namespace)	Your Service Namespace	Optional	Specifies the namespace for organizational purposes.
header (x-bronto-tags)	Tags	Optional	Specifies the tags to apply to logs. A tag is a key-value pair applied to a log to hold metadata about that log. Each tag is a label consisting of a key and a required value.

The table below lists the parameters used to determine the Bronto dataset associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-name	HTTP Header
x-bronto-log-name	HTTP Header
kubernetes.annotations.logs.bronto.io/dataset	Log Metadata
service.name	Log Metadata
service_name	Log Metadata
kubernetes.annotations.service_name	Log Metadata
kubernetes.labels.app.kubernetes.io/name	Log Metadata
kubernetes.container_name	Log Metadata

The table below lists the parameters used to determine the Bronto collection associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-namespace	HTTP Header
x-bronto-logset	HTTP Header
kubernetes.annotations.logs.bronto.io/collection	Log Metadata
service.namespace	Log Metadata
service_namespace	Log Metadata

Finally the table below lists the parameters used to assign tags to datasets, ordered from highest to lowest precedence.

Parameter Name	Parameter Type	Example
x-bronto-tags	HTTP Header	x-bronto-tags: tag1=value1,tag2=value2,…
kubernetes.annotations.tags.logs.bronto.io/<TAG_NAME>	Log Metadata	kubernetes.annotations.tags.logs.bronto.io/tag1: value1

Verify Log Collection

Once you have applied your configuration and restarted Fluent Bit, you c

brew install fluent-bit

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Configurate Fluent Bit

After installation, Fluent Bit requires an output configuration to communicate with the Bronto system.

/opt/homebrew/etc/fluent-bit.conf

[SERVICE]
    flush           10
    daemon          off
    log_level       info

[INPUT]
    name            tail
    path            /path/to/your/logs
    tag             <OPTIONAL_LOG_TAG>
    refresh_interval 5
    mem_buf_limit   5MB
    skip_long_lines on

[OUTPUT]
    name            http
    tls             on
    match           *
    host            ingestion.<REGION>.bronto.io
    port            443
    format          json_lines
    compress        gzip
    header          x-bronto-api-key <YOUR_API_KEY>
    header          x-bronto-service-name <YOUR_SERVICE_NAME>
    header          x-bronto-service-name-namespace <YOUR_SERVICE_NAMESPACE>
    header          x-bronto-tags: <key1=value1,key2=value2>

Parameter	Value	Requirement	Description
name	HTTP	Required	Specifies the output plugin used by Fluent Bit.
tls	on	Required	Enables the use of TLS for secure communication.
host	ingestion<REGION>.bronto.io	Required	The Bronto endpoint responsible for ingesting log data. Supported regions: EU & US.
port	443	Required	Specifies the network port for communication.
format	json_lines or msgpack	Required	Specify the data format to be used in the HTTP request body, by default it uses msgpack.
compress	gzip	Optional	Recommended. Compresses the payload in GZIP format. Bronto supports and recommends using gzip for efficient data transmission.
header (x-bronto-service-name)	Your Service Name	Required	Specifies the name of the service.
header (x-bronto-service-namespace)	Your Service Namespace	Optional	Specifies the namespace for organizational purposes.
header (x-bronto-tags)	Tags	Optional	Specifies the tags to apply to logs. A tag is a key-value pair applied to a log to hold metadata about that log. Each tag is a label consisting of a key and a required value.

The table below lists the parameters used to determine the Bronto dataset associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-name	HTTP Header
x-bronto-log-name	HTTP Header
kubernetes.annotations.logs.bronto.io/dataset	Log Metadata
service.name	Log Metadata
service_name	Log Metadata
kubernetes.annotations.service_name	Log Metadata
kubernetes.labels.app.kubernetes.io/name	Log Metadata
kubernetes.container_name	Log Metadata

The table below lists the parameters used to determine the Bronto collection associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-namespace	HTTP Header
x-bronto-logset	HTTP Header
kubernetes.annotations.logs.bronto.io/collection	Log Metadata
service.namespace	Log Metadata
service_namespace	Log Metadata

Finally the table below lists the parameters used to assign tags to datasets, ordered from highest to lowest precedence.

Parameter Name	Parameter Type	Example
x-bronto-tags	HTTP Header	x-bronto-tags: tag1=value1,tag2=value2,…
kubernetes.annotations.tags.logs.bronto.io/<TAG_NAME>	Log Metadata	kubernetes.annotations.tags.logs.bronto.io/tag1: value1

Verify log collection

Once you have applied your configuration and restarted Fluent Bit, you can expect to see your log data being ingested to Bronto and accessible via the Search page.

To make Fluent Bit available on every node, it should be installed as a DaemonSet. The recommended way to deploy Fluent Bit is with the official Helm Chart: https://github.com/fluent/helm-charts

To add the Fluent Helm Charts repo use the following command

helm repo add fluent https://fluent.github.io/helm-charts

To validate that the repo was added you can run helm search repo fluent to ensure the charts were added. The default chart can then be installed by running the following

helm upgrade --install fluent-bit fluent/fluent-bit

Configure Fluent Bit

After installation, Fluent Bit requires an output configuration to communicate with the Bronto system.

[SERVICE]
    daemon             off
    flush              10
    log_level          info
    parsers_file       /fluent-bit/etc/parsers.conf
    parsers_file       /fluent-bit/etc/conf/custom_parsers.conf
    http_server        on
    http_listen        0.0.0.0
    http_port          2020
    health_check       on

[INPUT]
    name               tail
    path               /var/log/containers/*.log
    multiline.parser   docker, cri
    tag                kube.*
    mem_buf_limit      5MB
    skip_long_lines    on

[INPUT]
    name               systemd
    tag                host.*
    systemd_filter     _SYSTEMD_UNIT=kubelet.service
    read_from_tail     on

[FILTER]
    name                kubernetes
    match               kube.*
    merge_Log           on
    keep_log            off
    k8s-logging.parser  on
    k8s-logging.exclude on

[OUTPUT]
    name                http
    tls                 on
    match               kube.*
    host                ingestion.<REGION>.bronto.io
    port                443
    format              json_lines
    compress            gzip
    header              x-bronto-api-key <YOUR_API_KEY>

[OUTPUT]
    name                http
    tls                 on
    match               host.*
    host                ingestion.<REGION>.bronto.io
    port                443
    format              json_lines
    compress            gzip
    header              x-bronto-api-key <YOUR_API_KEY>
    header              x-bronto-service-name-namespace <YOUR_SERVICE_NAMESPACE>
    header              x-bronto-tags: <key1=value1,key2=value2>

Parameter	Value	Requirement	Description
name	HTTP	Required	Specifies the output plugin used by Fluent Bit.
tls	on	Required	Enables the use of TLS for secure communication.
host	ingestion<REGION>.bronto.io	Required	The Bronto endpoint responsible for ingesting log data. Supported regions: EU & US.
port	443	Required	Specifies the network port for communication.
format	json_lines or msgpack	Required	Specify the data format to be used in the HTTP request body, by default it uses msgpack.
compress	gzip	Optional	Recommended. Compresses the payload in GZIP format. Bronto supports and recommends using gzip for efficient data transmission.
header (x-bronto-service-name)	Your Service Name	Optional	Specifies the name of the service. Setting this header in a Kubernetes setup is not recommended.
header (x-bronto-service-namespace)	Your Service Namespace	Optional	Specifies the namespace for organizational purposes. Setting this header in a Kubernetes setup is recommended, with its value indicating the cluster from which the data is originating, e.g. clusterA-production-eu1
header (x-bronto-tags)	Tags	Optional	Specifies the tags to apply to all logs of the cluster. A tag is a key-value pair applied to a log to hold metadata about that log. Each tag is a label consisting of a key and a required value.

The table below lists the parameters used to determine the Bronto dataset associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-name	HTTP Header
x-bronto-log-name	HTTP Header
kubernetes.annotations.logs.bronto.io/dataset	Log Metadata
service.name	Log Metadata
service_name	Log Metadata
kubernetes.annotations.service_name	Log Metadata
kubernetes.labels.app.kubernetes.io/name	Log Metadata
kubernetes.container_name	Log Metadata

The table below lists the parameters used to determine the Bronto collection associated with the ingested data, ordered from highest to lowest precedence.

Parameter Name	Parameter Type
x-bronto-service-namespace	HTTP Header
x-bronto-logset	HTTP Header
kubernetes.annotations.logs.bronto.io/collection	Log Metadata
service.namespace	Log Metadata
service_namespace	Log Metadata

Finally the table below lists the parameters used to assign tags to datasets, ordered from highest to lowest precedence.

Parameter Name	Parameter Type	Example
x-bronto-tags	HTTP Header	x-bronto-tags: tag1=value1,tag2=value2,…
kubernetes.annotations.tags.logs.bronto.io/<TAG_NAME>	Log Metadata	kubernetes.annotations.tags.logs.bronto.io/tag1: value1

Verify log collection

Once you have applied your configuration and restarted Fluent Bit, you can expect to see your log data being ingested to Bronto and accessible via the Search page.

Getting Started

Send Data

Search and Visualize

Monitors and Alerting

Usage Explorer

Account Management

Connect Fluent Bit to Bronto

Manual instructions

Add Server GPG Key

Add Repo

Install Package

Configure Fluent Bit

Verify Log Collection

Manual instructions

Add Server GPG Key

Add Repo

Install Package

Configure Fluent Bit

Verify Log Collection

Manual instructions

Add Repo

Install Package

Configure Fluent Bit

Verify Log Collection

Configure Fluent Bit

Verify Log Collection

Configurate Fluent Bit

Verify log collection

Configure Fluent Bit

Verify log collection

Getting Started

Send Data

Search and Visualize

Monitors and Alerting

Usage Explorer

Account Management

​Manual instructions

​Add Server GPG Key

​Add Repo

​Install Package

​Configure Fluent Bit

​Verify Log Collection

​Manual instructions

​Add Server GPG Key

​Add Repo

​Install Package

​Configure Fluent Bit

​Verify Log Collection

​Manual instructions

​Add Repo

​Install Package

​Configure Fluent Bit

​Verify Log Collection

​Configure Fluent Bit

​Verify Log Collection

​Configurate Fluent Bit

​Verify log collection

​Configure Fluent Bit

​Verify log collection

Manual instructions

Add Server GPG Key

Add Repo

Install Package

Configure Fluent Bit

Verify Log Collection

Manual instructions

Add Server GPG Key

Add Repo

Install Package

Configure Fluent Bit

Verify Log Collection

Manual instructions

Add Repo

Install Package

Configure Fluent Bit

Verify Log Collection

Configure Fluent Bit

Verify Log Collection

Configurate Fluent Bit

Verify log collection

Configure Fluent Bit

Verify log collection