[
https://issues.apache.org/jira/browse/AMBARI-8522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Szilard Nemethy reassigned AMBARI-8522:
---------------------------------------
Assignee: Szilard Nemethy
> 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
>
>
> 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)
