[
https://issues.apache.org/jira/browse/AMBARI-17784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-17784:
---------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk and branch-2.4
branch-2.4
{code}
commit 81fadc5e788be6b5115f3ac9c4fad9beb1336785
Author: Aravindan Vijayan <[email protected]>
Date: Wed Jul 20 10:39:57 2016 -0700
AMBARI-17784 : AMS Storm Sink: remove redundant information from kafka
offset metrics on storm-kafka (Jungtaek Lim via avijayan)
{code}
trunk
{code}
commit 2e873b6c4a4a7dae9c33f8df3e5f97ac61f73499
Author: Aravindan Vijayan <[email protected]>
Date: Wed Jul 20 10:48:09 2016 -0700
AMBARI-17784 : AMS Storm Sink: remove redundant information from kafka
offset metrics on storm-kafka (Jungtaek Lim via avijayan)
{code}
> 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)
