The Log4j configuration augmentation and override mechanism provided by Content Services still works in the same way, guaranteeing that additional log4j properties files with the appropriate suffix will be imported as augmentations/overrides of the original log4j2.properties configuration file.
Note: The suffix has changed from
-log4j.properties to -log4j2.properties.
Therefore, an additional configuration file named, for example
custom-log4j.properties has to be migrated to use the Log4j
2.x syntax, and finally be renamed to custom-log4j2.properties
instead so it’s picked up by the augmentation/override mechanism.