Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Async log4j2 log events are not counted accurately
See original GitHub issueMicrometer provides the Log4j2Metrics meter binder to add metrics for Log4j2 log events. Unfortunately the implementation is flawed. It is implemented as a filter, but filters can be invoked multiple times and must therefore not have any side effects.
In practice the filter is invoked multiple times by Log4j2 in many circumstances (e.g. in the presence of multiple and/or async loggers). The result is that the counter is increased multiple times for each single log event and the counter values become too high.
Issue Analytics
- State:
- Created 3 years ago
- Comments:22 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
As is not possible to use log4j filters to count log events properly I requested a statistics feature for the log4j team.
With some luck, we can have these counters direct from log4j API.
So, let’s became a log4j2 expert 😄
I just started a thread on log4j2 discussion list to see if is possible to use a filter for that use case.