# Fluent Bit documentation

<figure><img src="https://4080960765-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYLAade0z5f61r7oMWpvX%2Fuploads%2Fgit-blob-5223c066fa0bbfdee9d829c8426cb4f6b965c3cb%2Ffluent_bit_logo.png?alt=media" alt=""><figcaption></figcaption></figure>

[Fluent Bit](https://fluentbit.io) is a fast and lightweight telemetry agent for logs, metrics, and traces for Linux, macOS, Windows, and BSD family operating systems. Fluent Bit has been made with a strong focus on performance to allow the collection and processing of telemetry data from different sources without complexity.![](https://static.scarf.sh/a.png?x-pxid=71f0e011-761f-4c6f-9a89-38817887faae)

## Features

* High performance: High throughput with low resources consumption
* Data parsing
  * Convert your unstructured messages using Fluent Bit parsers: [JSON](https://docs.fluentbit.io/manual/data-pipeline/parsers/json), [Regex](https://docs.fluentbit.io/manual/data-pipeline/parsers/regular-expression), [LTSV](https://docs.fluentbit.io/manual/data-pipeline/parsers/ltsv) and [Logfmt](https://docs.fluentbit.io/manual/data-pipeline/parsers/logfmt)
* Metrics support: Prometheus and OpenTelemetry compatible
* Reliability and data integrity
  * [Backpressure](https://docs.fluentbit.io/manual/administration/backpressure) handling
  * [Data buffering](https://docs.fluentbit.io/manual/data-pipeline/buffering) in memory and file system
* Networking
  * Security: Built-in TLS/SSL support
  * Asynchronous I/O
* Pluggable architecture and [extensibility](https://docs.fluentbit.io/manual/fluent-bit-for-developers/library_api): Inputs, Filters and Outputs:
  * Connect nearly any source to nearly any destination using preexisting plugins
  * Extensibility:
    * Write input, filter, or output plugins in the C language
    * Wasm: [Wasm Filter Plugins](https://docs.fluentbit.io/manual/fluent-bit-for-developers/wasm-filter-plugins) or [Wasm Input Plugins](https://docs.fluentbit.io/manual/fluent-bit-for-developers/wasm-input-plugins)
    * Write [Filters in Lua](https://docs.fluentbit.io/manual/data-pipeline/filters/lua) or [Output plugins in Golang](https://docs.fluentbit.io/manual/fluent-bit-for-developers/golang-output-plugins)
* [Monitoring](https://docs.fluentbit.io/manual/administration/monitoring): Expose internal metrics over HTTP in JSON and [Prometheus](https://prometheus.io/) format
* [Stream Processing](https://docs.fluentbit.io/manual/stream-processing/overview): Perform data selection and transformation using basic SQL queries
  * Create new streams of data using query results
  * Aggregation windows
  * Data analysis and prediction: Time series forecasting
* Portable: Runs on Linux, macOS, Windows and BSD systems

### Release notes

For more details about changes in each release, refer to the [official release notes](https://fluentbit.io/announcements/).

If you are upgrading from the Fluent Bit `4.2` series, start with [What's new in Fluent Bit v5.0](https://docs.fluentbit.io/manual/installation/whats-new-in-fluent-bit-v5.0) and [Upgrade notes](https://docs.fluentbit.io/manual/installation/upgrade-notes).

## Fluent Bit, Fluentd, and CNCF

Fluent Bit is a [CNCF](https://www.cncf.io/) graduated sub-project under the umbrella of [Fluentd](https://www.fluentd.org).

Fluent Bit was originally created by [Eduardo Silva](https://www.linkedin.com/in/edsiper/) and is now sponsored by [Chronosphere](https://chronosphere.io/). As a CNCF-hosted project, it's a fully vendor-neutral and community-driven project.

## License

Fluent Bit, including its core, plugins, and tools, is distributed under the terms of the [Apache License v2.0](https://github.com/fluent/fluent-bit?tab=Apache-2.0-1-ov-file#readme).


---

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