You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Tom Beerbower (JIRA)" <ji...@apache.org> on 2012/11/20 06:53:58 UTC

[jira] [Created] (AMBARI-1026) Resolve overlap between JMX and Ganglia metrics

Tom Beerbower created AMBARI-1026:
-------------------------------------

             Summary: Resolve overlap between JMX and Ganglia metrics
                 Key: AMBARI-1026
                 URL: https://issues.apache.org/jira/browse/AMBARI-1026
             Project: Ambari
          Issue Type: Sub-task
            Reporter: Tom Beerbower
            Assignee: Tom Beerbower


Ensure that the same metrics are not provided by both the JMX and Ganglia provider.  If JMX provides a point in time metric, it should not also be provided by Ganglia.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (AMBARI-1026) Resolve overlap between JMX and Ganglia metrics

Posted by "Tom Beerbower (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Beerbower updated AMBARI-1026:
----------------------------------

    Attachment: AMBARI-1026.patch
    
> Resolve overlap between JMX and Ganglia metrics
> -----------------------------------------------
>
>                 Key: AMBARI-1026
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1026
>             Project: Ambari
>          Issue Type: Sub-task
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>         Attachments: AMBARI-1026.patch
>
>
> Ensure that the same metrics are not provided by both the JMX and Ganglia provider.  If JMX provides a point in time metric, it should not also be provided by Ganglia.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira