Documentation Index
Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt
Use this file to discover all available pages before exploring further.
You can use Fluent Bit to send logs to Chronosphere Observability Platform. To do
so, add an
HTTP output plugin
that specifies your Observability Platform tenant as its destination.
Example configuration
To route logs from Fluent Bit to Observability Platform, Chronosphere recommends
configuring an HTTP output plugin with the following parameters and values:
YAML configuration
Classic configuration
pipeline:
...
outputs:
- name: http
match: "kube.*"
alias: Chronosphere
host: TENANT
port: 443
uri: /api/v1/data/logs/ingest
header: "API-Token ${API_TOKEN}"
format: json
compress: gzip
json_date_format: iso8601
json_date_key: TIME
tls: true
tls.verify: true
tls.debug: 1
net.keepalive: true
net.keepalive_idle_timeout: 30s
net.connect_timeout: 10s
net.connect_timeout_log_error: true
net.keepalive_max_recycle: 2000
[OUTPUT]
Name http
Match kube.*
Alias Chronosphere
Host TENANT
Port 443
URI /api/v1/data/logs/ingest
Header API-Token ${API_TOKEN}
Format json
Compress gzip
json_date_format iso8601
json_date_key TIME
tls On
tls.verify On
tls.debug 1
net.keepalive On
net.keepalive_idle_timeout 30s
net.connect_timeout 10s
net.connect_timeout_log_error On
net.keepalive_max_recycle 2000
-
-
- Replace
TIME with the value you assigned to timestamps in your
log normalization settings.
If you didn’t set up log normalization for timestamps, replace TIME
with timestamp.
