[
https://issues.apache.org/jira/browse/LOG4J2-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204026#comment-17204026
]
Ralph Goers commented on LOG4J2-2937:
-------------------------------------
[~gengyuanzhe] That is a very good observation. However, I believe whatever is
implemented should be flexible enough to handle it. For example in Flume's case
the counters for Sinks, Sources, and Channels capture different things but they
are all counters. So for the base Appender counter it could include total
events logged and a counter for each logging level. That might need to be in a
Map though since custom logging levels are allowed. To implement this I would
recommend looking at what Flume did and cannibalizing as much as possible.
> Provide counters to measure log rate
> ------------------------------------
>
> Key: LOG4J2-2937
> URL: https://issues.apache.org/jira/browse/LOG4J2-2937
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: Dennys Fredericci
> Priority: Major
> Attachments: image-2020-09-28-21-10-13-850.png
>
>
> As a Log4j API user will be really nice to have a way to get the number of
> log calls for each level without any instrumentation or bytecode
> manipulation, something native from log4j API.
> Once this interface is implemented this can be exposed through JMX or used by
> other libraries to send the log rate to monitoring systems such as Datadog,
> NewRelic, Dynatrace, etc. :)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
