[
https://issues.apache.org/jira/browse/LOG4J2-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-163:
---
Attachment: (was: async-throughput-comparison.jpg)
> Create asynchronous Logger for low-laten
[
https://issues.apache.org/jira/browse/LOG4J2-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-163:
---
Attachment: async-throughput-comparison.jpg
> Create asynchronous Logger for low-latency logging
[
https://issues.apache.org/jira/browse/LOG4J2-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-163:
---
Attachment: async-perf-comparison.png
Just for fun I attached a graph comparing the throughput perfor
Werner created LOG4J2-190:
--
Summary: Bug in BaseConfiguration.addLoggerAppender(..)
Key: LOG4J2-190
URL: https://issues.apache.org/jira/browse/LOG4J2-190
Project: Log4j 2
Issue Type: Bug
Werner created LOG4J2-189:
--
Summary: AsynchAppender: "blocking" parameter doesn't work
Key: LOG4J2-189
URL: https://issues.apache.org/jira/browse/LOG4J2-189
Project: Log4j 2
Issue Type: Bug
Werner created LOG4J2-188:
--
Summary: The "appender-ref" functionality doesn't work perfectly
in the AsynchAppender
Key: LOG4J2-188
URL: https://issues.apache.org/jira/browse/LOG4J2-188
Project: Log4j 2
From what I could see you plan to edit the rolling file appender so it
can take a custom action on some events (roll over when already rolled
over files is > X) at which point files are pushed to another system.
Rolling file appender would continue to do what it does natively. I
think a better
