[
https://issues.apache.org/jira/browse/OAK-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855752#comment-15855752
]
Stefan Egli commented on OAK-5594:
----------------------------------
a generel remark on this change and on the other data in the consolidated
listener stats: the output when looking at the [system
console|http://localhost:8080/system/console/jmx/org.apache.jackrabbit.oak%3Aname%3DConsolidated+Event+Listener+statistics%2Ctype%3DConsolidatedListenerStats]
is indeed very large. Already for the {{ListenerStats}}, but now also for the
{{LeaderBoard}}. I still think having the paths as part of the LeaderBoard is
useful. But I'm wondering if there would be any other option in terms of
formatting it in the system console, so that this becomes manageable again.
[~mreutegg], [~chetanm], wdyt, any idea? Generally, should we port this to
1.6.1?
> leaderboard of consolidated listener stats should show path as well
> -------------------------------------------------------------------
>
> Key: OAK-5594
> URL: https://issues.apache.org/jira/browse/OAK-5594
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Affects Versions: 1.6.0
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Fix For: 1.7.0, 1.8
>
>
> The consolidated listener stats has a leaderboard section which sorts the
> leaders by cumulative processTime. This is useful information, however the
> className of the listener does not always allow to identify the culprit.
> Consider Sling's JcrResourceListener - which is created for each (group of)
> ResourceChangeListener. The leaderboard will only show (a number of)
> {{JcrResourceListener}} as the className and not which ResourceChangeListener
> is underneath.
> Ideally each listener could provide more details as to who is 'behind' itself
> - similarly to the
> [EventListenerMBean.getToString|https://github.com/apache/jackrabbit/blob/27dbe3c81c5b6d67c5fa7a50a53e7450218079a2/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/jmx/EventListenerMBean.java#L33].
> But atm that sometimes produces rather a lot of output.
> A simpler way might be to just add a column {{paths}} - that would show the
> same as in the {{ListenerStats}} table.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
