[ https://issues.jboss.org/browse/WFWIP-127?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-127: ----------------------------------- First, with the updated dev branch that excludes metrics without numeric types, jgroups metrics go from 354 to 180: {code} curl http://localhost:9990/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | grep subsystem | cut -d_ -f 3 | sort | uniq -c 10 activemq 1 average 180 channel 1 controller 7 jberet 10 number 18 server 7 thread 5 worker 8 workmanager {code} 2nd improvement specific to jgroups would be check that its statistics-enabled[1] attribute is working as expected. I would expect that the metrics attached to the channel resource have values only when the channel's statistics-enabled is true. [~pferraro] Could you please confirm that this is the case? However, I am not sure about exposing only a subset of a metrics for a given subsystem. The steps to monitor metrics are: 1. query all metrics that are available 2. select the ones you are interested in from the monitoring tool and monitor only those. Having a huge number of metrics is an UX issue for the monitoring tool. But I found that counter-intuitive to fix this UX issue by having the app server specifies which metrics are of interest to the monitoring tool. [1] http://wildscribe.github.io/WildFly/14.0//subsystem/jgroups/channel/ee/in... -- This message was sent by Atlassian Jira (v7.12.1#712002)