Thanks everyone for the feedback! I hope I'll be able to implement a decent chunk of the many ideas.
I made some mockups to see how this would work. Screenshot of MBeans tab in JConsole: http://imm.io/11SFm When running "${JAVA_HOME}/bin/jconsole -pluginpath log4j-core-2.0.jar", you would see this: http://imm.io/11SFU (Essentially a text editor in JConsole that would allow you to edit the configuration remotely.) (This can all be done without dependencies on external libraries, it only uses stuff that is in the JDK.) Feedback is always welcome. -Remko ________________________________ From: Scott Deboy <scott.de...@gmail.com> To: Log4J Developers List <log4j-dev@logging.apache.org> Sent: Thursday, April 4, 2013 1:57 AM Subject: Re: JMX support in log4j2 I could imagine it could be handy to connect via JMX and retrieve the last X number of warn/error/fatal events via JMX...sounds like a JMXAppender though more than stats.. On Wed, Apr 3, 2013 at 9:38 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: Core should be fine. I just don't want to drag any dependencies into the API or Core other than what is absolutely necessary. Although you can make the dependencies optional at some point that confuses users. > > >For statistics I could imagine things like the total number of events. The >number of non-filtered events. The number of events that were directed to a >specific Appender, and such. > >Ralph > > > >On Apr 3, 2013, at 2:53 AM, Remko Popma wrote: > >These all look doable. >> >> >>About Statistics from various components, @Ralph, anything in particular >>you'd like to see? (If not, it is pretty easy to add them later.) >> >> >>Also, can the JMX related classes go into core or does this need a separate >>module? I would prefer core so that this is always available for users without fiddling with extra jars. >>Thoughts? >> >> >> >>On 2013/04/03, at 9:35, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> >> >>Features I would like to see in JMX: >>>1. Show all the LoggerContexts and their configurations. >>>2. Ability to modify a configuration (this should involve cloning the >>>current configuration, modifying it and then replacing the prior >>>configuration with the new one). >>>3. Statistics from various components. >>>4. Display log output on the JMX console (at least the StatusLogger output). >>> >>> >>> >>> >>> >>> >>> >>> >>>On Apr 2, 2013, at 12:38 AM, Remko Popma wrote: >>> >>>I would like to take a stab at implementing JMX support for log4j2. >>>> >>>>What features would you like to see with regards to JMX? Ideas are welcome! >>> >
