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

Hudson commented on AMBARI-8522:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit-docker #443 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/443/])
AMBARI-8522. Enable Flume metrics sink to AMS. Missing stack changes. (Szilard 
Nemethy via mpapirkovskyy) (mpapyrkovskyy: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=86b0ce46c69c22d1bb23e976fcea06cd93dae8ea)
* 
ambari-server/src/main/resources/stacks/HDP/2.2/services/AMS/configuration/ams-site.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/templates/flume-metrics2.properties.j2
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/scripts/flume.py
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/configuration/flume-env.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/scripts/params.py


> Enable Flume metrics sink to AMS
> --------------------------------
>
>                 Key: AMBARI-8522
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8522
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-metrics
>    Affects Versions: 2.0.0
>            Reporter: Erik Bergenholtz
>            Assignee: Szilard Nemethy
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8522.patch
>
>
> Ambari Metrics needs to be able to collect metrics from Flume 
> (https://github.com/apache/flume)
> -Create a TimelineMetricsSink class that implements MonitorService.
> Look at org.apache.flume.instrumentation.GangliaServer
> - Configure Flume if Ambari Metrics is deployed to use TimelineMetricsSink in 
> its classpath
> http://flume.apache.org/FlumeUserGuide.html#custom-reporting
> - Look into how to support GET queries for FLUME agent, 
> stacks/HDP/2.0.6/services/FLUME/metrics.json
> User is unaware of group name and Channel name for a given agent.
> *Key points*:
> - Store the appId = 'flume"
> - Allow for regex queries in GET API, example if flume metrics looks like: 
> "agentName.groupName.channelName.MetricName", user can query AMS API as 
> (\\w)\+.(\\w)\+.(\\w)\+.metricName
> This transforms to a LIKE SQL clause which needs to be added to the timeline 
> service API
> http://phoenix.apache.org/language/index.html#expression



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

Reply via email to