# Buffer

Previously defined in the [Buffering](https://docs.fluentbit.io/manual/1.8/concepts/buffering) concept section, the `buffer` phase in the pipeline aims to provide a unified and persistent mechanism to store your data, either using the primary in-memory model or using the filesystem based mode.

The `buffer` phase already contains the data in an immutable state, meaning, no other filter can be applied.

![](https://3741101272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LKKSx-3LBTCtaHbg0gl-887967055%2Fuploads%2Fgit-blob-ba80a23b4f579320e29e8e7faf0de64d0f74f894%2Flogging_pipeline_buffer%20\(1\)%20\(1\)%20\(2\)%20\(2\)%20\(2\)%20\(2\)%20\(2\)%20\(2\)%20\(2\)%20\(1\).png?alt=media)

{% hint style="info" %}
Note that buffered data is not raw text, it's in Fluent Bit's internal binary representation.
{% endhint %}

Fluent Bit offers a buffering mechanism in the file system that acts as a *backup system* to avoid data loss in case of system failures.


---

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

```
GET https://docs.fluentbit.io/manual/1.8/concepts/data-pipeline/buffer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.