[
https://issues.apache.org/jira/browse/SLING-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839564#comment-15839564
]
Bertrand Delacretaz commented on SLING-5410:
--------------------------------------------
Additional comments from a different discussion thread,
http://markmail.org/message/ti4dtelm4mxsi6tn :
Ian mentions that we should upgrade to dropwizard Metrics 3.2 once
https://github.com/dropwizard/metrics/issues/539 is fixed.
The Sling core should optionally work with metrics disabled - the Sling Metrics
library can provide a no-op implementation for this, but that's not
configurable so far IIUC.
> Identify component where important Metrics can be collected
> -----------------------------------------------------------
>
> Key: SLING-5410
> URL: https://issues.apache.org/jira/browse/SLING-5410
> Project: Sling
> Issue Type: Task
> Components: Engine
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
>
> With SLING-4080 we now have support for collecting various kinds of metrics
> in performant way.
> As a next step we would need to identify those parts of Sling engine and
> request processing logic where we can collect important metrics. Such metric
> should help
> # Sling system administrator to monitor key aspects of Sling
> # Allow us as developers to get insight into critical parts and help in doing
> further optimization
> Once identified we can then add required metric collection logic to those
> parts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
