Allow severity-based log message filtering in PluginProcessor#4063
Merged
vy merged 3 commits intoapache:2.xfrom Mar 17, 2026
Merged
Conversation
b893c7c to
cff6451
Compare
Contributor
Author
vy
reviewed
Mar 16, 2026
Member
vy
left a comment
There was a problem hiding this comment.
@treyfarmigoni, it is very rare we encounter PRs as complete as yours. Thanks so much for your due diligence. 💯
I've dropped some minor remarks, but I see no showstoppers.
...re/src/main/java/org/apache/logging/log4j/core/config/plugins/processor/PluginProcessor.java
Outdated
Show resolved
Hide resolved
Member
|
@treyfarmigoni, would you mind pulling in the changes from |
Contributor
Author
|
@vy - Conflicts should now be resolved. Thank you! |
vy
approved these changes
Mar 17, 2026
PluginProcessor
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
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.

Allow filtering in printMessage based on log4j.plugin.processor.minAllowedMessageKind
Issue details discussed here
#3380 (reply in thread)
Checklist
2.xbranch if you are targeting Log4j 2; usemainotherwise./mvnw verifysucceeds (the build instructions)src/changelog/.2.x.xdirectory