[GEODE-1275] Refactor custom appenders to move dynamic functionality into managers

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: configuration, logging
• Labels: AlertAppender Log4j2 LogWriterAppender log4j2.xml
• Assignee: Kirk Lund
• Reporter: Kirk Lund
• Created: 22/Apr/16 16:33
• Updated: 10/Mar/17 20:44
• Resolved: 10/Mar/17 20:44

Description

Presently Geode dynamically creates, adds and removes AlertAppender and LogWriterAppender by manipulating log4j2 core API. We should move the bulk of the Appender functionality to internal Manager classes and just leave the Appenders registered with log4j2 during the life of the JVM.

This allows us to enable and configure our Appenders via log4j2.xml and control the Cache-controlled lifecycle completely within our own classes without having to add and remove custom Appender instances.

The code would then become simpler. Our custom code would not have to invoke log4j2 core APIs and a User would have control over configuring our use of log4j2 via the .xml file. Presently, a User cannot configure our AlertAppender or LogWriterAppender in log4j2.xml.