Shweta, The GC metrics are sent over with the name of the garbage collector in the metric name. In metrics.json it allows defining metrics with a wildcard, but you can't define widgets without knowing the metric name ahead of time. Currently it is a limitation of Ambari and you can't get the GC metrics displayed with the example provided.
-Bryan On Sun, Feb 7, 2016 at 11:22 AM, shweta <[email protected]> wrote: > Hi All, > > I can see that sample metrics.json has couple of attributes for GC. > "metrics/jvm/gc/runs/$1": { > "metric": "jvm.gc.runs.(\\w+)", > "pointInTime": true, > "temporal": true > }, > "metrics/jvm/gc/time/$1": { > "metric": "jvm.gc.time.(\\w+)", > "pointInTime": true, > "temporal": true > } > > However widget.json does not have anything for information regarding > gathering GC parameters. I would like to gather GC metrics also. When I see > on Ambari I cannot get a widget for same probably for same reason. > Is there any specific reason why GC params are not included in widget.json > as given in > https://cwiki.apache.org/confluence/display/NIFI/Ambari+Metrics. > > Thanks, > Shweta > > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/Difference-between-metrics-json-and-widgets-json-for-Ambari-Service-tp7197.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
