Yeah - Given that ticket it is obvious to me that this class should be moved to another module. I don’t think moving it to Chainsaw or Flume is the correct thing to do. For now, I would put it into log4j-samples, either under log4j-server or in its own module.
Note that a Flume event consists of a Map of “headers” and a body. The body is the result of calling layout.getFormattedMessage() and the headers generally would contain values from the ThreadContextMap as well as fields from the Map if the LogEvent contains a MapMessage. So in many cases parsing the message isn’t necessary since the fields are usually already available as headers. Ralph > On Jan 2, 2024, at 3:30 PM, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > Hi Ralph, > > On Tue, 2 Jan 2024 at 13:21, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> >> Why is it included if it isn’t used? > > Apparently this was added by Mikael in: > https://issues.apache.org/jira/browse/LOG4J2-1986 > > There were no significant changes/bug fixes after the initial submission. > > Piotr
