[
https://issues.apache.org/jira/browse/AMBARI-17784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383879#comment-15383879
]
Hadoop QA commented on AMBARI-17784:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12818753/AMBARI-17784-v1-on-top-of-AMBARI-17725.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-metrics/ambari-metrics-storm-sink
ambari-metrics/ambari-metrics-storm-sink-legacy.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7917//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7917//console
This message is automatically generated.
> 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)
