Hi Jeff, Thanks for your suggestion. I ended up doing it slightly different (see my response to Thad Humphries).
However, I’ll keep your idea in mind because the ability to both include a standard configuration in the app and also optionally modifying this configuration via an external config file seems interesting. I can easily see that we might want to do this in the future. With kind regards Piers -- Piers Uso Walter <piers.wal...@ilink.de> ilink Kommunikationssysteme GmbH Kurfuerstendamm 67, 10707 Berlin, Germany +49 (30) 28526-185 > Am 21.03.2024 um 07:19 schrieb jeffrey.tho...@t-systems.com: > > Hi Piers, > > I am not from Log4j Team - just a user like you :) > > We have a similar situation with internal distribution configuration and > external "customer" configuration. > > What we are now doing is programmatically creating a CompositeConfiguration > with the internal config and external config and reconfiguring Log4j early in > our startup. > > Cheers, Jeff
