[
https://issues.apache.org/jira/browse/LOG4J2-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203595#comment-17203595
]
Remko Popma commented on LOG4J2-2937:
-------------------------------------
Isn't there often some temporal aspect to such counters?
I imagine people would want to use counters not just to answer the question
"how many events did we log since the system started" but also "how many events
did we log between 9:00 and 9:01", and "can we graph the events/second between
9:00 and 17:00"?
Simply incrementing a counter will not be sufficient to answer questions like
that. (Although Flume's implementation is nicely thread-safe.)
[~dennysfredericci], can you clarify your requirements? What do you intend to
do with these numbers? What questions are you trying to answer?
> 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
>
> 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)
