[
https://issues.apache.org/jira/browse/AMBARI-8420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241720#comment-14241720
]
Hudson commented on AMBARI-8420:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1165 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1165/])
AMBARI-8420. Add Amabri Metric Provider to get metrics from AMS. Check
liveliness. (swagle) (swagle:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d2bc0ac8193e13988879bde4078a7406bacd0935)
*
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProvider.java
> 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)
