I've implemented a similar servlet, but chose instead to read in the logback.xml file and parse it using a DOM. The UI shows some pieces of the configuration file and hides some complexity in others. Writes the file back out when saved. Relies on scan="true" to reconfigure the logger when the file is saved. From: logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of James Morgan Sent: Tuesday, March 22, 2011 12:28 PM To: logback-user@qos.ch Subject: [logback-user] Equivalent of LogManager.getCurrentLoggers() ? Hi, I've recently started using LogBack with SLF4j instead of Log4J and have run into a problem. We currently have a simple servlet that gets deployed with all our running apps which allows us to change the Logging level and add loggers at runtime. Im currently trying to convert the current implementation to support LogBack with SLF4j and have run into problems. One of the core parts of the servlet gets all loggers in order to create a GUI where things can be controlled from. It uses this factory class to get all loggers, org.apache.log4j.LogManager.getCurrentLoggers(). I've looked through the code and online but have yet to find an alternative solution. Do you know if there is away to get all loggers simplar to the given factory methods? Or am i heading in the wrong directiopn with this, is there alternatives to find this informaiton out about current loggers? Thanks for any help you can provide. Cheers James