I didn’t realize that Log4J ships with an XML appender.
Solution was: specify an XML appender in the logging configuration file, include that output XML file as an entity into a well formed XML file, then parse the XML using your favorite technique.
The other methods had the following limitations:
- Apache Chainsaw – not automated enough
- jdbc – poor performance in a high performance distributed app