Fluent Bit
Configure the Fluent Bit OpenTelemetry output plugin to forward container and host logs from your Kubernetes cluster or infrastructure to Sazabi.
About
Forward container and host logs from any Fluent Bit deployment into Sazabi using Fluent Bit's built-in OpenTelemetry output plugin. Sazabi receives the logs over OTLP/HTTPS — no additional plugin installation required for Fluent Bit v2.0 or later.
Prerequisites
- Fluent Bit v2.0 or later. The
opentelemetryoutput plugin ships by default in v2.0+. - Your Sazabi intake URL, shown above — open the log source and copy the Intake URL from its setup screen (the public key is embedded in the URL)
Set up in the dashboard
Add the Sazabi output to your Fluent Bit config
Add the following [OUTPUT] block to your Fluent Bit configuration and wire it to your existing [INPUT] sources:
[OUTPUT]
name opentelemetry
match *
host <your intake hostname>
port 443
logs_uri /v1/logs
tls on
tls.verify onReplace <your intake hostname> with the hostname portion of your intake URL (shown above), without the https:// scheme or path.
For Kubernetes deployments using Helm, add the output block under config.outputs in your values file.
Fluent Bit v2.0 or later is required. Earlier versions do not include the
opentelemetry output plugin.
Restart Fluent Bit
Restart the Fluent Bit process or roll the DaemonSet so the new output configuration takes effect. Check Fluent Bit logs for any connection or TLS errors during startup.
Set up with the CLI
You can also register the Fluent Bit log source with the Sazabi CLI (installed and authenticated — see CLI reference).
Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):
sazabi log-sources create fluent_bit --mode connectionlessThe command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run sazabi log-sources get <log-source-id> at any time to reprint the endpoint, or sazabi log-sources list to see every log source in the project.
Verify
After Fluent Bit restarts, generate some log activity (or wait for the next log flush from your inputs). Open the Intake page in the Sazabi dashboard and confirm records from the Fluent Bit source appear within a minute or two.
Troubleshooting
No records after restarting — Check Fluent Bit output for TLS or DNS errors on the opentelemetry output. Confirm host is the hostname only (no https://, no trailing slash) and port is 443.
Plugin not found error — The opentelemetry output plugin is only available in Fluent Bit v2.0 and later. Check your version with fluent-bit --version and upgrade if needed.
Partial log delivery — If your [INPUT] sources use match tags, confirm the [OUTPUT] block's match pattern covers those tags (or use * to forward all inputs).