ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-8420) Add Amabri Metric Provider to get metrics from AMS
Date Wed, 10 Dec 2014 19:37:12 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Siddharth Wagle updated AMBARI-8420:
------------------------------------
    Attachment: AMBARI-8420.patch

> Add Amabri Metric Provider to get metrics from AMS
> --------------------------------------------------
>
>                 Key: AMBARI-8420
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8420
>             Project: Ambari
>          Issue Type: Task
>    Affects Versions: 2.0.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8420.patch
>
>
> *Requirements*:
> - Add a AmbariMetricPropertyProvider similar to the GangliaPropertyProvider
> - Change the request from RRD to HTTP with ATS as the endpoint.
> - Implement a strategy to allow query for precision data vs aggregate data based on time
range. This strategy should be configurable/tunable.
> - The Provider should detect where the AMS is deployed automatically.
> - The metrics.json from Ganglia remains exactly the same for the new provider since the
properties in the request as well as Hadoop metrics are the same.
> - Add unit test to verify all GET calls are working
> - This needs to consider multiple AMS instances - need strategy for load balancing across
instances.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message