Re: Profile controlled filtering

Definitely don't recommend implementing the interfaces directly as they're not guaranteed to be backwards compatible, but the abstract classes generally are. On 27 February 2017 at 14:43, Remko Popma wrote: > One option is to create a custom Log4j2 Filter. Your custom

Re: Profile controlled filtering

One option is to create a custom Log4j2 Filter. Your custom Filter would only be "active" if it detects it's in the correct environment, otherwise it would return NEUTRAL from all `filter(...)` methods. CompositeFilter is final so you can't subclass it but perhaps you can create a wrapper

RE: Profile controlled filtering

Maybe there is a smarter way to do this in Log4J, but the low-tech approach I have deployed in the past was to simply have 2 different xml configuration files (we only had Prod Vs. Dev) and deploy the one that matched the setting. But these days, we unify everything and it's basically just a

Profile controlled filtering

Hello, we want replace our legacy proprietary logging framework. One important feature of our current logging framework is the so called 'profile controlled filtering'. There exist different filtering profiles like 'production', 'test' or 'development'. The profile to use is selected by a