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

Hudson commented on AMBARI-17784:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #5348 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5348/])
AMBARI-17784 : AMS Storm Sink: remove redundant information from kafka 
(avijayan: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2e873b6c4a4a7dae9c33f8df3e5f97ac61f73499])
* 
ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java
* 
ambari-metrics/ambari-metrics-storm-sink-legacy/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java
* 
ambari-metrics/ambari-metrics-storm-sink-legacy/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java
* 
ambari-metrics/ambari-metrics-storm-sink/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java


> AMS Storm Sink: remove redundant information from kafka offset metrics on 
> storm-kafka
> -------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17784
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17784
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.4.0
>            Reporter: Jungtaek Lim
>            Assignee: Jungtaek Lim
>         Attachments: AMBARI-17784-v1-on-top-of-AMBARI-17725.patch, 
> AMBARI-17784-v1.patch
>
>
> This is follow-up issue for AMBARI-17725.
> After AMBARI-17725, we can distinguish cluster metrics and topology metrics, 
> which makes us possible to topology name and component name as variables for 
> templatized dashboard.
> But kafkaOffset metrics still have kafka topic and partition information to 
> middle of metric name which make us hard to pick. Since worker host and 
> worker port, and task id is not needed for kafkaOffset metrics, we can get 
> rid of those things from only kafkaOffset metrics.



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

Reply via email to