Hi, You can add a filter on MBean in the cfg file of your collector.
Here an example with Camel MBean only: https://github.com/apache/karaf-decanter/blob/main/collector/jmx/src/main/cfg/org.apache.karaf.decanter.collector.jmx-camel.cfg regards, François fpa...@apache.org Le 01/06/2021 à 11:07, Steven Huypens a écrit : > Hi, > > Enabling the JMX-collector leads to a very high CPU load in our > application, making it impossible to use. I'm not sure, but I think > especially the org.apache.karaf MBeans are expensive to harvest, maybe > because of the size of our application (>900 bundles). > > It would be very useful if we could configure which MBeans we are > interested in. > > Kind regards, > Steven > > > On Mon, May 3, 2021 at 6:14 AM Jean-Baptiste Onofre <j...@nanthrax.net > <mailto:j...@nanthrax.net>> wrote: > > Hi Daniel, > > JMX collector polls all MBeans attributes. However Prometheus > appender only expose metrics (numeric) on the Prometheus servlet: > > http://localhost:8181/decanter/prometheus > <http://localhost:8181/decanter/prometheus> > > As the generated JMX JSON is "more" than just numeric, it’s > possible that you don’t have the metrics. > > You can check the JMX JSON using another kind of appender (like > log appender or elasticsearch). > I can add kind of "json introspection" on the Prometheus appender > to "force" some JSON fields as metrics (gauge). > > Regards > JB > > > Le 2 mai 2021 à 22:24, Daniel Las <daniel....@empirica.io > <mailto:daniel....@empirica.io>> a écrit : > > > > Hi, > > > > I installed Decanter 2.7.0 on Karaf 4.2.11 with JMX collector > and Prometheus appender features. I uncommented > "object.name.system=java.lang:*" in > org.apache.karaf.decanter.collector.jmx-local.cfg. > > > > Where can I find JVM metrics like current heap memory usage? > > > > Regards > > -- > > Daniel Łaś > > >
