[
https://issues.apache.org/jira/browse/OAK-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493728#comment-14493728
]
Michael Dürig commented on OAK-2755:
------------------------------------
Re. 1., 2.: Can't we use the object name used to register the MBean to related
the various parts? Otherwise let's come up with the concept of an observer id
that could be exposed and would be the same for related MBeans.
Re. 3. - 5.: Instead of accessing all those components directly, each of those
should register its own MBean with the relevant information. The consolidated
view should then operate on those MBeans instead of on the components directly.
This separates the monitoring concern from the main concern and more
importantly would prevent exposing internals impacting further evolution.
bq. All thos cast server the purpose of extracting important details if
possible. Which IMO is fine for monitoring kind of logic.
Yes but then it should not leak into the main components, which it does through
the need of opening access to internal data structures.
> Consolidated JMX view of all EventListener related statistics
> -------------------------------------------------------------
>
> Key: OAK-2755
> URL: https://issues.apache.org/jira/browse/OAK-2755
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Labels: monitoring, observation
> Fix For: 1.0.13, 1.3.0
>
> Attachments: OAK-2755-2.patch, OAK-2755.patch,
> consolidated-listener-stats-2.png, consolidated-listener-stats.png
>
>
> Oak Observation support exposes a {{EventListenerMBean}} [1] which provide
> quite a bit of details around registered observation listeners. However in a
> typical application there would be multiple listeners registered. To simplify
> monitoring it would be helpful to have a _consolidated_ view of all listeners
> related statistics.
> Further the stats can also include some more details which are Oak specific
> * Subtree paths to which the listener listens to - By default JCR Api allows
> single path however Oak allows a listener to register to multiple paths
> * If listener is enabled to listen to cluster local and cluster external
> changes
> * Size of queue in BackgroundObserver
> * Distribution of change types present in the queue - Local, External etc
> [1]
> https://github.com/apache/jackrabbit/blob/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/jmx/EventListenerMBean.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
