[
https://issues.apache.org/jira/browse/OAK-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012786#comment-15012786
]
Chetan Mehrotra commented on OAK-3478:
--------------------------------------
{quote}
The bean "Oak Repository Statistics-simple" produces the right type of stats,
but I think the the "per second" approach wont work as the sequence of numbers
from the existing TimeSeries follows the pattern
0,0,0,0,0,0,0,761000000,0,0,0,0,0,0,0 etc. If the monitoring tool happens to
query either side of the 716000000 value, then it get 0. To get 761000000 it
has to query at exactly the correct time. You could use the per minute
value.... but it would be better not to re-invent the research in this area and
look at what others have already proven to work in production.
{quote}
Makes sense. Opened OAK-3654 to determine effort required to provide a metric
based implementation. Would close this issue as Wont Fix then
> Provide JMX Beans for Oak that can be monitored by external tooling.
> --------------------------------------------------------------------
>
> Key: OAK-3478
> URL: https://issues.apache.org/jira/browse/OAK-3478
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, jcr, lucene, query
> Affects Versions: 1.3.7
> Reporter: Ian Boston
> Assignee: Chetan Mehrotra
> Fix For: 1.3.11
>
> Attachments: OAK-3478-v1.patch
>
>
> The Current JMX beans, while ok in the Sling Web Console are hard if not
> impossible to monitor with external tooling, as external tooling will poll
> for current values, ideally from named attributes containing primitive types.
> Those values containing timers, counters or gauges. Timers timing an
> operation. Counters counting an operation. Guages measuring an instantaneous
> value.
> The request is to provide a small number of JMX beans that can be configured
> into an external monitoring tool like AppDynamics, Ganglia, NewRelic, Splunk
> etc etc, which in turn will provide long term time series and statistics.
> Primitive values of this form can also be graphed with ease in JConsole,
> VisualVM etc. A improvement for the Sling Web Console might be to add a
> Console that can maintain a TimeSeries graph of any JMX bean by object name
> in the same way Ganglia, AppDynamics does, however that may be duplicating
> existing functionality.
> The Metrics Library could be considered to provide the above functionality
> for all JMX beans and monitoring, although its footprint at 111K might be
> considered too big as an additional dependency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
