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

Hudson commented on AMBARI-20758:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7495 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7495/])
AMBARI-20758 Aggregate local metrics for minute aggregation time window (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2e27f661947cb72f4004eb17903caf1f76012468])
* (edit) ambari-metrics/ambari-metrics-host-aggregator/pom.xml


> Aggregate local metrics for minute aggregation time window
> ----------------------------------------------------------
>
>                 Key: AMBARI-20758
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20758
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-metrics
>    Affects Versions: 2.5.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-20758_7.patch
>
>
> - Abstract Sink checks if there is local known monitor port available to 
> write (e.g.: 61888)
> - Handshake / Ping to make sure its the monitor and is accepting writes
> - Start sending metrics only to the monitor
> - Monitor sends metrics at the global send interval (1 minute) with all the 
> granularity of the sink
> - Monitor aggregates first interval (5 min) data and sends it every interval 
> seconds. (5 min)
> - The monitor interface look the same as that of collector (http server: 
> maybe Flask)
> - Security concerns need to be addressed as well. (https/spnego?)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to