Re: Employing BurstFilter and AsyncFilter for batch append ops

Actually, several of the Appenders deal with batches of events, but they get the events 1 at a time and queue them internally. When an application logs an event each event goes through the chain of filters and appenders and every appender that gets the event can do whatever it wants with it. Log

Employing BurstFilter and AsyncFilter for batch append ops

Hi, While implementing an *org.apache.logging.log4j.core.Appender*, the only *append()* method that needs to be implemented takes a single *LogEvent* argument: *void append(LogEvent event)*. This makes it impossible to handle and resolve batch append operations at the appender level. This results

[jira] [Commented] (LOG4J2-1933) Not able to init config with JsonConfiguration class while the json config nodes are in random order

[ https://issues.apache.org/jira/browse/LOG4J2-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047523#comment-16047523 ] Roman Sosnin commented on LOG4J2-1933: -- Sorry I have no time for this. Hoped you cou