[jira] [Commented] (AMBARI-3725) Check for overlaps in metrics between JMX and Ganglia try to get all point in time metrics from JMX.

["Tom Beerbower (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817422#comment-13817422 ] 

Tom Beerbower commented on AMBARI-3725:
---------------------------------------

Fixed a number of cases where metrics were being retrieved from both Ganglia and JMX or where they were available from JMX but not specified in the JMX properties description.  Also, there were a number of cases where we had inconsistencies in metric names, such as case changes, from the v1 properties description to the v2 properties description.

The patch includes unit tests that check for inconsistencies like these.

> Check for overlaps in metrics between JMX and Ganglia try to get all point in time metrics from JMX.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-3725
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3725
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>         Attachments: AMBARI-3725.patch
>
>
> Look for overlaps like ...
> ganglia_properties.json
> {code}
>      "metrics/jvm/memHeapUsedM":{
>         "metric":"jvm.metrics.memHeapUsedM",
>         "pointInTime":true,
>         "temporal":true
>       },
> {code}
> jmx_properties.json
> {code}
>      "metrics/jvm/memHeapUsedM":{
>         "metric" : "Hadoop:service=JobTracker,name=jvm.memHeapUsedM",
>         "pointInTime" : true,
>         "temporal" : false
>       },
> {code}
> Try to keep point in time metrics in JMX only.



--
This message was sent by Atlassian JIRA
(v6.1#6144)