> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fluent Bit

> Configure the Fluent Bit OpenTelemetry output plugin to forward container and host logs from your Kubernetes cluster or infrastructure to Sazabi.

[All Fluent Bit integration capabilities](https://docs.sazabi.com/catalogs/integrations/fluent-bit)

## 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 `opentelemetry` output 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

**Step 1**

### 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:

```ini title="fluent-bit.conf" theme={"system"}
[OUTPUT]
    name              opentelemetry
    match             *
    host              <your intake hostname>
    port              443
    logs_uri          /v1/logs
    tls               on
    tls.verify        on
```

Replace `<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.

> [!WARNING]
>
> Fluent Bit v2.0 or later is required. Earlier versions do not include the
> `opentelemetry` output plugin.

**Step 2**

### 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.

**Step 3**

### Hand off the change

If this configuration is version-controlled, commit it on a new branch, push it, and open a pull request. Otherwise apply it directly to your Fluent Bit deployment. Keep the intake URL and any keys in environment variables or a secret store, and commit only configuration that references them.

## Set up with the CLI

You can also register the Fluent Bit log source with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/log-sources.md)).

Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):

```bash theme={"system"}
sazabi log-sources create fluent_bit --mode manual
```

The 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](https://docs.sazabi.com/guides/instrument/intake.md) 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).

## Further reading

> [card] [Intake](https://docs.sazabi.com/guides/instrument/intake.md)
>
> See per-source ingestion volume and health.

> [card] [OpenTelemetry Collector](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/otel-collector.md)
>
> Use the OpenTelemetry Collector as an alternative pipeline agent.

> [card] [Log sources](https://docs.sazabi.com/catalogs/log-sources.md)
>
> Browse the full log source catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.