[
https://issues.apache.org/jira/browse/OAK-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492659#comment-14492659
]
Will McGauley commented on OAK-2755:
------------------------------------
This information has proven to be very valuable in the past when working with
customers who experienced problems where observation queues were overflowing.
I think this information is critical to determine which event listeners in a
busy system are the bottleneck, and will help customers tune their observation
listeners appropriately. I can also say that if the stats available in jmx
beans change over time customers will generally be ok with that, they just want
to be able to monitor their systems accurately and are happy to adjust their
scripts as needed when things change. If internals change and new values are
being reported that should be acceptable, I don't really see the risk. The
most important part is to provide the data to the users so they can make
accurate decisions.
> 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)
