[
https://issues.apache.org/jira/browse/SLING-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101424#comment-15101424
]
Ian Boston commented on SLING-5410:
-----------------------------------
imho Metrics data should be aggregated externally in systems like App Dynamics,
Kibana, Splunk, New Relic, Ganglia. Aggregating the data on the cluster leader
will obfuscate issues with individual instances. (and the cluster leader is not
stable).
> 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)
