[jboss-jira] [JBoss JIRA] (WFWIP-127) Subsystem jgroups exposes 354 metrics, no way to expose subset of metrics

[Jeff Mesnil (Jira)]

    [ https://issues.jboss.org/browse/WFWIP-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656667#comment-13656667 ] 

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/index.html#attr-statistics-enabled

> Subsystem jgroups exposes 354 metrics, no way to expose subset of metrics
> -------------------------------------------------------------------------
>
>                 Key: WFWIP-127
>                 URL: https://issues.jboss.org/browse/WFWIP-127
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: MP Metrics
>            Reporter: Rostislav Svoboda
>            Assignee: Jeff Mesnil
>            Priority: Critical
>
> Subsystem jgroups exposes 354 metrics
> There is no way to expose subset of metrics for subsystem
> standalone.xml
> {code}
> curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | wc -l
>      109
> curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | grep subsystem | cut -d_ -f 3 | sort | uniq -c
>    7 batch
>    1 datasources
>    7 ejb3
>    6 io
>    8 jca
>    1 request
>   11 transactions
>   12 undertow
> {code}
> standalone-full-ha.xml
> {code}
> curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | wc -l
>      497
> curl http://localhost:10090/metrics 2>/dev/null | grep -v TYPE | grep -v HELP | grep subsystem | cut -d_ -f 3 | sort | uniq -c
>    7 batch
>    1 datasources
>    7 ejb3
>    6 io
>    8 jca
>  354 jgroups
>   10 messaging
>    1 request
>   11 transactions
>   18 undertow
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)