@DiegoTavares @roulaoregan-spi Would love to get your thoughts and some additional testing on this.

Config has changed a lot from 1.x -> 2.x. I've tested it locally and everything seems to be in line with what was logged previously but it would be great to get confirmation.

It's not like we're pressed to fix this right away, as our version is not on the list of affected versions for the infamous zero day, but I agree it's about time to upgrade it.

The changes look good to me. We're integrating it into our dev environment soon testing during Jan before releasing it to production on the end of Jan.

looks like need to upgrade to 2.17
https://logging.apache.org/log4j/2.x/index.html

@bcipriano this PR needs some love

@DiegoTavares Thanks for the reminder. I've brought it up to date with master. Only issue with that merge is the HEALTH log that was added recently. I've added that into the new log4j2.properties file.

Please take another look, if it's looking good let's get it merged.

Hey, what's the status on this. We're looking to get cleaner logs out of opencue and it would be great to have this merged.

Thanks

Graham

@grimjak Thanks for the reminder! Yes, this has been sitting too long and we should get it merged finally.

I've brought the change up to date with master, just going to do a final check with some of the others to make sure we're good to merge.

Thanks for the prompt response. I've applied your changes to our test deployment which is mostly up to date with master. I don't see anything in health.log although that could easily be something I missed. Otherwise the changes all seem to work fine

@grimjak Thanks for trying it out! Indeed, for health.log I had an appender but no logger set up. That's been corrected now.

TSC confirmed we are good to merge this now.