Ian Boston created OAK-3478:
-------------------------------
Summary: 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
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)
