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

# FluentD and FluentBit

> Stream FluentD and FluentBit logs and metrics to Mezmo Pipelines using HTTP output plugins for SaaS or Forward plugins for Edge.

## Description

You can stream FluentD and FluentBit logs and metrics to Mezmo Pipelines using HTTP output plugins for SaaS pipelines, and Forward output plugins for [Mezmo Edge Pipelines](/mezmo-edge/mezmo-edge-pipelines-for-local-data).

## Configuration

#### FluentD

To send your FluentD data to a Mezmo Pipeline, add to a `v1`  config file, a `match`  with the `http`  output plugin configured as follows:

```bash theme={null}
# Modify the match criteria to be more specific if needed.
# Modify the endpoint to include your pipeline_id.
# Modify the headers authorization key to match the key generated from the pipeline source.

# The FluentD source decoding method in your pipeline should be set to ndjson.

<match **>
  @type http
  @id   http1
  endpoint https://pipeline.mezmo.com/v1/<YOUR ROUTE ID>
  open_timeout 2
  headers {"Authorization": "<YOUR GENERATED ACCESS KEY>"}
  <format>
    @type json
  </format>
  <buffer>
    flush_at_shutdown true
    flush_interval 10s
  </buffer>
</match>

```

Note that, while the `format` says `json` here, because the setting `json_array`[defaults to `false`](https://docs.fluentd.org/output/http#content_type) , FluentD will be emitting `json`  objects without the enclosing array. Therefore, **Decoding Method** should be set to `ndjson` .

#### FluentBit

FluentBit can be configured to send data to any Mezmo Pipeline HTTP source. Please see the examples for both Classic and YAML configuration below, making the appropriate substitutions for your source path and key.

For YAML, add a new output in under the pipeline group:

```yaml theme={null}
pipeline:
    outputs:
      - name: http
        match: '*'
        host: 'pipeline.mezmo.com'
        uri: '/v1/<YOUR ROUTE ID>'
        header: 'Authorization: <YOUR GENERATED ACCESS KEY>'
        tls: 'on'
        port: 443
        format: 'json_lines'

```

The output is added to classic configurations by adding an `Output` block to the top level as follows:

```bash theme={null}
[output]
    name http
    match *
    host pipeline.mezmo.com
    uri <URL PATH FROM YOUR SOURCE CONFIGURATION>
    header "Authorization: <YOUR GENERATED ACCESS KEY>"
    tls on
    port 443
    format json_lines

```

### Mezmo Configuration Options

| Option          | Description                                                      |
| --------------- | ---------------------------------------------------------------- |
| Decoding Method | The decoding method to use for converting frames to data events. |