# Data pipeline

The Fluent Bit data pipeline incorporates several specific concepts. Data processing flows through the pipeline following these concepts in order.

{% @mermaid/diagram content="graph LR
accTitle: Fluent Bit data pipeline
accDescr: A diagram of the Fluent Bit data pipeline, which includes input, a parser, a filter, a buffer, routing, and various outputs.
A\[Input] --> B\[Parser]
B --> C\[Filter]
C --> D\[Buffer]
D --> E((Routing))
E --> F\[Output 1]
E --> G\[Output 2]
E --> H\[Output 3]" %}

## Inputs

[Input plugins](https://docs.fluentbit.io/manual/4.1/data-pipeline/inputs) gather information from different sources. Some plugins collect data from log files, and others gather metrics information from the operating system. There are many plugins to suit different needs.

## Parser

[Parsers](https://docs.fluentbit.io/manual/4.1/data-pipeline/parsers) convert unstructured data to structured data. Use a parser to set a structure to the incoming data by using input plugins as data is collected.

## Filter

[Filters](https://docs.fluentbit.io/manual/4.1/data-pipeline/filters) let you alter the collected data before delivering it to a destination. In production environments you need full control of the data you're collecting. Using filters lets you control data before processing.

## Buffer

The [buffering](https://github.com/fluent/fluent-bit-docs/blob/master/concepts/buffering.md) phase in the pipeline aims to provide a unified and persistent mechanism to store your data, using the primary in-memory model or the file system-based mode.

## Routing

[Routing](https://docs.fluentbit.io/manual/4.1/data-pipeline/router) is a core feature that lets you route your data through filters, and then to one or multiple destinations. The router relies on the concept of [tags](https://docs.fluentbit.io/manual/4.1/key-concepts#tag) and [matching](https://docs.fluentbit.io/manual/4.1/key-concepts#match) rules.

## Output

[Output plugins](https://docs.fluentbit.io/manual/4.1/data-pipeline/outputs) let you define destinations for your data. Common destinations are remote services, local file systems, or other standard interfaces.
