Skip to content
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

concepts: filter: update for style #1486

Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 11 additions & 6 deletions concepts/data-pipeline/filter.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
---
description: Modify, Enrich or Drop your records
description: Modify, enrich or drop your records
---

# Filter

In production environments we want to have full control of the data we are collecting, filtering is an important feature that allows us to **alter** the data before delivering it to some destination.
In production environments you want to have full control of the data being collected.
esmerel marked this conversation as resolved.
Show resolved Hide resolved
Filtering lets you alter the collected data before delivering it to a destination.

```mermaid
graph LR
Expand All @@ -20,10 +21,14 @@ graph LR
style C stroke:darkred,stroke-width:2px;
```

Filtering is implemented through plugins, so each filter available could be used to match, exclude or enrich your logs with some specific metadata.
Filtering is implemented through plugins. Each available filter could be used to
esmerel marked this conversation as resolved.
Show resolved Hide resolved
match, exclude or enrich your logs with specific metadata.
esmerel marked this conversation as resolved.
Show resolved Hide resolved

We support many filters, A common use case for filtering is Kubernetes deployments. Every Pod log needs to get the proper metadata associated
Fluent Bit support many filters. A common use case for filtering is Kubernetes
deployments. Every pod log needs the proper metadata associated.
esmerel marked this conversation as resolved.
Show resolved Hide resolved

Very similar to the input plugins, Filters run in an instance context, which has its own independent configuration. Configuration keys are often called **properties**.
Like input plugins, filters run in an instance context, which has its own independent
configuration. Configuration keys are often called _properties_.

For more details about the Filters available and their usage, please refer to the [Filters](https://docs.fluentbit.io/manual/pipeline/filters) section.
For more details about the Filters available and their usage, see
[Filters](https://docs.fluentbit.io/manual/pipeline/filters).