> For the complete documentation index, see [llms.txt](https://docs.fluentbit.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fluentbit.io/manual/5.0/administration/configuring-fluent-bit/yaml.md).

# YAML configuration files

![](https://static.scarf.sh/a.png?x-pxid=864c6f0e-8977-4838-8772-84416943548e)

In Fluent Bit v3.2 and later, YAML configuration files support all of the settings and features that [classic configuration files](/manual/5.0/administration/configuring-fluent-bit/classic-mode.md) support, plus additional features that classic configuration files don't support, like processors.

YAML configuration files support the following top-level sections:

* `env`: Configures [environment variables](/manual/5.0/administration/configuring-fluent-bit/yaml/environment-variables-section.md).
* `includes`: Specifies additional YAML configuration files to [include as part of a parent file](/manual/5.0/administration/configuring-fluent-bit/yaml/includes-section.md).
* `service`: Configures global properties of the Fluent Bit [service](/manual/5.0/administration/configuring-fluent-bit/yaml/service-section.md).
* `pipeline`: Configures active [`inputs`, `filters`, and `outputs`](/manual/5.0/administration/configuring-fluent-bit/yaml/pipeline-section.md).
* `parsers`: Defines [custom parsers](/manual/5.0/administration/configuring-fluent-bit/yaml/parsers-section.md).
* `multiline_parsers`: Defines [custom multiline parsers](/manual/5.0/administration/configuring-fluent-bit/yaml/multiline-parsers-section.md).
* `plugins`: Defines paths for [custom plugins](/manual/5.0/administration/configuring-fluent-bit/yaml/plugins-section.md).
* `upstream_servers`: Defines [nodes](/manual/5.0/administration/configuring-fluent-bit/yaml/upstream-servers-section.md) for output plugins.
* `extensions`: Carries [settings for external tooling](#extensions-section) that Fluent Bit parses but doesn't act on.

{% hint style="info" %}
YAML configuration is used in the smoke tests for containers. An always-correct up-to-date example is here: <https://github.com/fluent/fluent-bit/blob/master/packaging/testing/smoke/container/fluent-bit.yaml>.
{% endhint %}

## `extensions` section

The `extensions` section is available in Fluent Bit version 5.1 and greater.

Use this section to store settings that belong to tooling around Fluent Bit, such as a management agent or a deployment system, in the same file as your pipeline. Fluent Bit parses and retains the section, but nothing in the data pipeline reads it. Adding it doesn't change how Fluent Bit collects, processes, or delivers data.

Unlike other sections, `extensions` accepts arbitrarily nested maps, and preserves the type of each value. Group settings under a key that identifies the tool that consumes them:

```yaml
service:
  flush: 1
  log_level: info

extensions:
  opamp:
    endpoint: 127.0.0.1:4318
    insecure: true
  deployment:
    config_version: 12345
```

Nested values are only accepted in this section. Using a nested map elsewhere fails with `variant values are only valid in the extensions section`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fluentbit.io/manual/5.0/administration/configuring-fluent-bit/yaml.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.