pipeline: add note to explicit the limitation of conditional processing by using filter as processor #1828
Conversation
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
…ng by using filter as processor Signed-off-by: Carlos Neto <[email protected]>
patrick-stephens
approved these changes
Jul 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Conditional Processing feature does not work with Filter as Processor. This is not clearly mentioned in the documentation, which can be confusing for users who expect conditional rules to apply to Filters like Lua and Modify when used as processors.
I reported this limitation in the fluent-bit GitHub repo, including configuration examples and steps to reproduce the issue. Until this feature is supported, the documentation should clarify this gap.