We have a requirement that we would like to centrally manage logging configuration files and push these out to applications as and when needed. So my questions are. Is it possible to reconfigure using Joran at runtime rather than one at initialisation time, are there any potential side effects? It would be fairly simple to write some code to listen for JMS or on a port to receive a message which would receive a Logback configuration, but would would be the message format? A logback configuration xml file how do then then pass that into Joran? The sending on messages is no problem as we would just create our own appender or use something like JMS appender to centralise log data collection. Any ideas would be great? Cheers Paul -- View this message in context: http://www.nabble.com/Local-Remote-config-management-at-runtime-tp21745848p2... Sent from the Logback User mailing list archive at Nabble.com.
Has no one out there got any ideas? Can logback be configured programatically at runtime and can this configuration be updated without the need to bounce the server? Paul G wrote:
We have a requirement that we would like to centrally manage logging configuration files and push these out to applications as and when needed.
So my questions are. Is it possible to reconfigure using Joran at runtime rather than one at initialisation time, are there any potential side effects?
It would be fairly simple to write some code to listen for JMS or on a port to receive a message which would receive a Logback configuration, but would would be the message format? A logback configuration xml file how do then then pass that into Joran?
The sending on messages is no problem as we would just create our own appender or use something like JMS appender to centralise log data collection.
Any ideas would be great?
Cheers Paul
-- View this message in context: http://www.nabble.com/Local-Remote-config-management-at-runtime-tp21745848p2... Sent from the Logback User mailing list archive at Nabble.com.
Hello Paul, This is a good idea. There is no reason why should not be able to accomplish this on your own. You can invoke Joran at any time passing the configuration file as reference to a file, a file name, any input stream including StringInputStream, or a list of SAXEvents. If you wish to change one or two aspects in the logging environment (logger level, change the layout of a given appender) you could also apply the changes programmatically without going through Joran. Cheers, Paul G wrote:
We have a requirement that we would like to centrally manage logging configuration files and push these out to applications as and when needed.
So my questions are. Is it possible to reconfigure using Joran at runtime rather than one at initialisation time, are there any potential side effects?
It would be fairly simple to write some code to listen for JMS or on a port to receive a message which would receive a Logback configuration, but would would be the message format? A logback configuration xml file how do then then pass that into Joran?
The sending on messages is no problem as we would just create our own appender or use something like JMS appender to centralise log data collection.
Any ideas would be great?
Cheers Paul
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch
participants (2)
-
Ceki Gulcu -
Paul G