-
Notifications
You must be signed in to change notification settings - Fork 541
pipeline: processors: README: general cleanup #1886
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
alexakreizinger
merged 2 commits into
master
from
alexakreizinger/sc-136289/update-fluent-bit-docs-pipeline-processors
Jul 9, 2025
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,38 +1,29 @@ | ||
| # Processors | ||
|
|
||
| Processors are components that modify, transform, or enhance data as it flows | ||
| through Fluent Bit. Unlike [filters](../filters/README.md), processors are | ||
| tightly coupled to inputs, which means they execute immediately and avoid | ||
| creating a performance bottleneck. | ||
| Processors are components that modify, transform, or enhance data as it flows through Fluent Bit. Unlike [filters](../filters/README.md), processors are tightly coupled to inputs, which means they execute immediately and avoid creating a performance bottleneck. | ||
|
|
||
| Additionally, filters can be implemented in a way that mimics the behavior of | ||
| processors, but processors can't be implemented in a way that mimics filters. | ||
| Additionally, filters can be implemented in a way that mimics the behavior of processors, but processors can't be implemented in a way that mimics filters. | ||
|
|
||
| {% hint style="info" %} | ||
|
|
||
| **Note:** Processors can be enabled only by using the YAML configuration format. Classic mode configuration format | ||
| doesn't support processors. | ||
| Processors are only compatible with the YAML configuration format. Classic mode configuration files don't support processors. | ||
|
|
||
| {% endhint %} | ||
|
|
||
| ## Available processors | ||
|
|
||
| Fluent Bit offers the following processors: | ||
|
|
||
| - [Content Modifier](content-modifier.md): Manipulate the content, metadata, and | ||
| attributes of logs and traces. | ||
| - [Content modifier](content-modifier.md): Manipulate the content, metadata, and attributes of logs and traces. | ||
| - [Labels](labels.md): Add, update, or delete metric labels. | ||
| - [Metrics Selector](metrics-selector.md): Choose which metrics to keep or discard. | ||
| - [OpenTelemetry Envelope](opentelemetry-envelope.md): Transform logs into an | ||
| OpenTelemetry-compatible format. | ||
| - [Sampling](sampling.md): Trace sampling designed with a pluggable architecture, | ||
| allowing easy extension to support multiple sampling strategies and backends. | ||
| - [Metrics selector](metrics-selector.md): Choose which metrics to keep or discard. | ||
| - [OpenTelemetry envelope](opentelemetry-envelope.md): Transform logs into an OpenTelemetry-compatible format. | ||
| - [Sampling](sampling.md): Apply head or tail sampling to incoming traces. | ||
| - [SQL](sql.md): Use SQL queries to extract log content. | ||
| - [Filters](filters.md): Any filter can be used as a processor. | ||
| - [Filters as processors](filters.md): Use filters as processors. | ||
|
|
||
| ## Features | ||
|
|
||
| Compatible processors include the following features: | ||
|
|
||
| - [Conditional Processing](conditional-processing.md): Selectively apply processors | ||
| to logs based on the value of fields that those logs contain. | ||
| - [Conditional processing](conditional-processing.md): Selectively apply processors to logs based on the value of fields that those logs contain. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.