[
https://issues.apache.org/jira/browse/LOG4J2-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677080#comment-16677080
]
Carter Kozak commented on LOG4J2-1137:
--------------------------------------
We would need to be careful about buffering events containing messages with
parameter references. A mechanism must exist to predictably allow parameters to
be garbage collected.
> Allow events to be buffered until something triggers and causes them to be
> logged.
> ----------------------------------------------------------------------------------
>
> Key: LOG4J2-1137
> URL: https://issues.apache.org/jira/browse/LOG4J2-1137
> Project: Log4j 2
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.4
> Reporter: Ralph Goers
> Priority: Major
>
> In many cases logging is filtered in production to reduce the overhead of
> logging. Unfortunately, this means that when an error occurs there may not be
> enough logging information available to diagnose the problem. On the other
> hand, if filtering is minimized then the amount of data being logged can be
> overwhelming.
> This enhancement would allow log events to be written to a buffer and not
> processed any further until a triggering event occurs. Once that trigger
> occurs all the events in the buffer would be logged in sequence and pass
> through the normal filtering process. Some log events that are deemed
> "special" would need to be allowed to bypass the buffer and immediately be
> processed.
> One way to accomplish this would be to add a new LogBuffer component to the
> configuration. If configured, the ReliabilityStrategies could be modified to
> work with the LogBuffer or a BufferingReliabilityWrapperStrategy could be
> created to wrap the existing strategies.
> Note - no code has been written for this yet. I'd want to figure out what the
> configuration might look like before starting.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
