If you make it a global filter it will get applied before the LogEvent is constructed. Please try that.
Remko Sent from my iPhone > On 9 Nov 2016, at 7:02, Benjamin Jaton <[email protected]> wrote: > > I am applying it on the root logger. > >> On Tue, Nov 8, 2016 at 12:47 PM, Matt Sicker <[email protected]> wrote: >> >> Where are you applying the filter? On the appender or somewhere else? >> >> On 8 November 2016 at 13:13, Benjamin Jaton <[email protected]> >> wrote: >> >>> hello, >>> >>> I was playing with log4j2 filters to generate a hash in groovy that I >> would >>> put in the threadcontext map, and then use in my log pattern: >>> >>> %d{yyyy-MM-dd HH:mm:ss} %-5p %c{1.}:%L - %m [%X{myhash}] >>> >>> But the hash is printed on the NEXT log message. >>> My understanding is that at this point the log message is already >> formatted >>> and final. >>> >>> Is there another way I can use a custom script where the log event can >>> actually be modified? >>> >>> Thanks, >>> Ben >>> >> >> >> >> -- >> Matt Sicker <[email protected]> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
