[
https://issues.apache.org/jira/browse/LOG4J2-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203755#comment-17203755
]
Remko Popma edited comment on LOG4J2-2937 at 9/29/20, 7:35 AM:
---------------------------------------------------------------
Thanks for the additional info. I agree that simple labeled, thread-safe
counters is the way to go.
I just wanted to clarify the trade-offs; I now believe the trade-off is a good
one.
was (Author: [email protected]):
Thanks for the additional info. I agree that simple labeled, thread-safe
counters is the way to go.
I just wanted to clarify the trade-offs; I believe the trade-off is a good one.
> 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)
