This is for Logs Classic, not Logs in Grail. Not sure if something similar might also apply?
In a Managed environment I have re-ordered the Log processing rules, so that the most they are matched, the higher they appear on the list. But now, after reading the documentation more carefully, it seams that for each Log entry, all rules seem to be processed. Which in my case doesn't apply, as almost all rules have a specific matcher.
Not sure what the impact on computing resources are exactly, but processing millions of log entries should make a difference.
So, is there a way to state that if a certain matcher is applied, the remaining rules can be skipped?
Antonio Sousa
