[jira] [Updated] (LOG4J2-207) JMX support for Log4j2

["Remko Popma (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remko Popma updated LOG4J2-207:
-------------------------------

    Attachment: LOG4J2-207-jmx-images.zip
                LOG4J2-207-jmx.patch

Please find attached files LOG4J2-207-jmx.patch and LOG4J2-207-jmx-images.zip.
The latter is used in the manual page, please unzip into src/site/resources/images.

This patch provides initial JMX support with MBeans for
StatusLogger, ContextSelector, LoggerContext, LoggerConfig and Appender.

A number of attributes of these objects can be viewed and some can also be modified in JMX tools like JConsole.

Also included is a simple client GUI that can be used to monitor the StatusLogger output and modify the configuration. 
The client GUI can run stand-alone or as a JConsole plug-in.

Maven needs to see the jconsole.jar during the build, so I modified core/pom.xml
and added two profiles because apparently on the mac, jconsole.jar lives in ${java.home}/../Classes/jconsole.jar,
not in ${java.home}/../lib/jconsole.jar.
I don't have a mac so I was unable to test this.
If this breaks the build, you could consider removing the ClientGUIJConsolePlugin.java file.
This is the only class that depends on jconsole.jar.

                
> JMX support for Log4j2
> ----------------------
>
>                 Key: LOG4J2-207
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-207
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Core, Documentation
>            Reporter: Remko Popma
>         Attachments: LOG4J2-207-jmx-images.zip, LOG4J2-207-jmx.patch
>
>
> Provide built-in support for JMX.
> Features wish-list (from the log4j-dev mailing list):
> 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).
> ----
> stats : (if using) rolling file - number rolls - long, time of last x 
> rolls - sometimes a node starts logging too much and we need to add to 
> number of max files or other action (could mean too many errors)
> number of err & fatal logs in last x2 hours
> where x, x2 are jmx properties with good defaults
> ----
> 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.
> ----
> I could imagine it could be handy to connect via JMX and retrieve the last
> X number of warn/error/fatal events via JMX..
> ----
> ability to "flushBuffers"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org