sundaybluesky commented on issue #3527:
URL:
https://github.com/apache/logging-log4j2/issues/3527#issuecomment-2721248503
Thanks @ppkarwasz for your information, I'll try the global filter option
and do performance test, then update the result.
--
This is an automated message from the Ap
ppkarwasz commented on issue #3527:
URL:
https://github.com/apache/logging-log4j2/issues/3527#issuecomment-2716983252
> Is this CustomFilter run in LogEvent consumer side or producer side? It
could introduce performance workload if filter logic is performed at consumer
side, as far as I kn
sundaybluesky commented on issue #3527:
URL:
https://github.com/apache/logging-log4j2/issues/3527#issuecomment-2716739763
@ppkarwasz
Is this CustomFilter run in LogEvent consumer side or producer side? It
could introduce performance workload if filter logic is performed at consumer
ppkarwasz commented on issue #3527:
URL:
https://github.com/apache/logging-log4j2/issues/3527#issuecomment-2713531070
@sundaybluesky,
Did you consider using [a custom
filter](https://logging.apache.org/log4j/2.x/manual/filters.html) instead?
Based on your code all you need is a filt
sundaybluesky opened a new issue, #3527:
URL: https://github.com/apache/logging-log4j2/issues/3527
AsyncLogger constructor access changed from public to package-private at
2.24.3 code change - https://github.com/apache/logging-log4j2/pull/3263 blocked
our CustomLogger instances initializati
