MichaelMorrisEst commented on issue #3074: URL: https://github.com/apache/logging-log4j2/issues/3074#issuecomment-2669089264
> > The use case is that when a certificate expires and is replaced that the SocketAppender can continue without the need for manual intervention (currently need to touch the config file in order to reload the cert or restart). > > A different angle: Accept a list of ~files~ URI sources to monitor in addition to the configuration file itself? > > <Configuration monitorInterval="60"> > <MonitorUri>file:///path/to/cert</MonitorUri> > </Configuration> Yes, that could work well. The URIs could be read in XmlConfiguration/JsonConfiguration and passed to AbstractConfiguration.initializeWatchers(...) in the same way as the monitorInterval is. The URIs could then be passed to WatchManager.watch(...) in addition to the config file, and the WatchManager.isModified() method returning true if the config file has changed or if any of the files given in the URIs have changed, thus triggering a reconfig. This could be a very tidy way to implement it, extending the existing WatchManager rather than implementing something new. @ppkarwasz what do yo think? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
