Take a look at the RewriteAppender (https://logging.apache.org/log4j/2.x/manual/appenders.html#RewriteAppender). That may be a good start.
Remko (Shameless plug) Every java main() method deserves http://picocli.info > On Feb 2, 2018, at 21:48, Walter Heestermans (TME) > <[email protected]> wrote: > > I take a look in that direction, true that the appender logic is not to be > amended, only the text to be logged, so converter should be enough. > > Regards > Walter > > -----Original Message----- > From: Chandra [mailto:[email protected]] > Sent: 02 February 2018 13:44 > To: [email protected] > Subject: RE: Extend daily log file appender > > I believe custom pattern converter should suffice in your case. You could > create a converter which encrypts the log event data. > > Reg, Chandra > >> On 2 Feb 2018, 5:53 PM +0530, Walter Heestermans (TME) >> <[email protected]>, wrote: >> We like to do the encryption outside the application logging,a nd >> centralized inside the logger >> >> Regards, >> Walter >> >> >> -----Original Message----- >> From: Chandra [mailto:[email protected]] >> Sent: 02 February 2018 12:30 >> To: [email protected]; [email protected] >> Subject: Re: Extend daily log file appender >> >> any issues to log encrypted data directly? >> >> Reg, Chandra >> >>> On 2 Feb 2018, 4:31 PM +0530, Walter Heestermans (TME) >>> <[email protected]>, wrote: >>> Hi, >>> >>> For GDPR we should have some log4 log appender (extended from daily log >>> file appender) that encrypts the log information. >>> >>> Anybody aware of some appender doing that? If not can somebody provide >>> sample to create own appender based on the default daily file logger? >>> >>> Regards >>> Walter >>> >>> >>> >>> This e-mail may contain confidential information. If you are not an >>> addressee or otherwise authorised to receive this message, you should not >>> use, copy, disclose or take any action based on this e-mail. If you have >>> received this e-mail in error, please inform the sender promptly and delete >>> this message and any attachments immediately. >> This e-mail may contain confidential information. If you are not an >> addressee or otherwise authorised to receive this message, you should not >> use, copy, disclose or take any action based on this e-mail. If you have >> received this e-mail in error, please inform the sender promptly and delete >> this message and any attachments immediately. > This e-mail may contain confidential information. If you are not an addressee > or otherwise authorised to receive this message, you should not use, copy, > disclose or take any action based on this e-mail. If you have received this > e-mail in error, please inform the sender promptly and delete this message > and any attachments immediately.
