-
Notifications
You must be signed in to change notification settings - Fork 4
Issue 30: Add Rule/Condition objects to allow specifying eventType based on multiple factors #31
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
base: main
Are you sure you want to change the base?
Conversation
…; Add ContainerRule & test; Add DefaultCondition; Make EnvironmentSource map immutable; change NLFPlugin to use Rules; change error message asserts to match new logic; add Rule interface; add RuleStub; add SyslogProcessNameCondition; add SyslogRule & test; remove processName validation from SyslogType; add TypeCondition; add TypeSuffixCondition
MoonBow-1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was a bit confused about the Predicate generic, but figured their use of the .test method.
A description of the PR would've been nice to have, since there is only an issue, which contains a request for a feature.
src/main/java/com/teragrep/nlf_01/condition/SyslogProcessNameCondition.java
Show resolved
Hide resolved
MoonBow-1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A question about the behavior of the test(ParsedEvent parsedEvent) method
src/main/java/com/teragrep/nlf_01/condition/SyslogProcessNameCondition.java
Outdated
Show resolved
Hide resolved
change SyslogProcessNameCondition match checks to final booleans
Fixes #30