From 23b437459094afe4a427a9f235f86f1738e53d76 Mon Sep 17 00:00:00 2001 From: Lynette Miles Date: Thu, 24 Oct 2024 11:45:33 -0700 Subject: [PATCH 1/2] concepts: filter: update for style Signed-off-by: Lynette Miles --- concepts/data-pipeline/filter.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/concepts/data-pipeline/filter.md b/concepts/data-pipeline/filter.md index c903b7c0a..132509871 100644 --- a/concepts/data-pipeline/filter.md +++ b/concepts/data-pipeline/filter.md @@ -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. +Filtering lets you alter the collected data before delivering it to a destination. ```mermaid graph LR @@ -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 +match, exclude or enrich your logs with specific metadata. -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. -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). From 6a8e4a0a1a5df296fd35f622282168d791dc55c7 Mon Sep 17 00:00:00 2001 From: esmerel <6818907+esmerel@users.noreply.github.com> Date: Fri, 25 Oct 2024 08:59:06 -0700 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Alexa Kreizinger Signed-off-by: esmerel <6818907+esmerel@users.noreply.github.com> --- concepts/data-pipeline/filter.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/concepts/data-pipeline/filter.md b/concepts/data-pipeline/filter.md index 132509871..c6c9eef81 100644 --- a/concepts/data-pipeline/filter.md +++ b/concepts/data-pipeline/filter.md @@ -4,7 +4,7 @@ description: Modify, enrich or drop your records # Filter -In production environments you want to have full control of the data being collected. +In production environments you need full control of the data you're collecting. Filtering lets you alter the collected data before delivering it to a destination. ```mermaid @@ -21,11 +21,11 @@ graph LR style C stroke:darkred,stroke-width:2px; ``` -Filtering is implemented through plugins. Each available filter could be used to -match, exclude or enrich your logs with specific metadata. +Filtering is implemented through plugins. Each available filter can be used to +match, exclude, or enrich your logs with specific metadata. Fluent Bit support many filters. A common use case for filtering is Kubernetes -deployments. Every pod log needs the proper metadata associated. +deployments. Every pod log needs the proper metadata associated with it. Like input plugins, filters run in an instance context, which has its own independent configuration. Configuration keys are often called _properties_.