Hi, Here are some reporters that work with Sling/Oak/AEM. [1]. They all look for components registered as implementing MetricsRegistry and then aggregate the data pumping it out to a reporter. They are all implemented as independent bundles. <imvho>TBH I would avoid pumping the metrics into JMX as JMX was designed for management, and not metrics. It might be able to cope with trivial metrics sets, but will likely start to consume unreasonable JVM resources with a production set of metrics.</imvho>.
Most of the reporters in [1] are simple wrappers round other 3rd party Metrics reporters. If you have a target not included in that list, its trivial to follow the same pattern. HTH Best Regards Ian 1 https://github.com/ieb/statsd-reporter-osgi https://github.com/ieb/prometheus-reporter-osgi https://github.com/ieb/influxdb-reporter-osgi https://github.com/ieb/gmond-osgi https://github.com/ieb/tsdb-reporter-osgi On 29 May 2017 at 12:48, Andrei Kalfas <[email protected]> wrote: > Hi, > > > By default this is the only mode. > > What would you guys rather prefer, have a different component peeks into > the metrics registry or change oak-core to deal with multiple reporters - > Jmx should be the default one. > > Thanks, > Andrei > >
