You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2017/12/13 11:05:00 UTC

[jira] [Comment Edited] (OAK-7055) Expose observation queue max length as metric

    [ https://issues.apache.org/jira/browse/OAK-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289099#comment-16289099 ] 

Marcel Reutegger edited comment on OAK-7055 at 12/13/17 11:04 AM:
------------------------------------------------------------------

More specifically, there is currently {{RepositoryStats.getObservationEventCount()}}, which is also exposed as a Meter. Similarly, {{RepositoryStats.getObservationQueueMaxLength()}} should get exposed as a Counter (actually a Gauge, but Oak's StatisticsProvider does not provide this).


was (Author: mreutegg):
More specifically, there is currently {{RepositoryStats.getObservationEventCount()}, which is also exposed as a Meter. Similarly, {{RepositoryStats.getObservationQueueMaxLength()}} should get exposed as a Counter (actually a Gauge, but Oak's StatisticsProvider does not provide this).

> Expose observation queue max length as metric
> ---------------------------------------------
>
>                 Key: OAK-7055
>                 URL: https://issues.apache.org/jira/browse/OAK-7055
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core-spi
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.8
>
>
> In addition to the number of events delivered to listener, the repository should also expose the observation queue max length as a metric. This will make it easier to monitor the health of the system, as the queue length is a rather important indicator whether listeners are progressing in a timely manner. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)