[LOG4J2-207] JMX support for Log4j2

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-beta5
• Component/s: Core, Documentation
• Assignee: Ralph Goers
• Reporter: Remko Popma
• Created: 11/Apr/13 17:37
• Updated: 20/Apr/13 00:32
• Resolved: 19/Apr/13 18:00

Description

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"

Issue Links

• is related to: LOG4J2-208 Merge log4j-async into log4j-core