Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-1137

Allow events to be buffered until something triggers and causes them to be logged.


    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.4
    • Fix Version/s: None
    • Component/s: Core
    • Labels:


      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.


          Issue Links



              • Assignee:
                ralph.goers@dslextreme.com Ralph Goers
              • Votes:
                0 Vote for this issue
                4 Start watching this issue


                • Created: