[
https://issues.apache.org/jira/browse/AMBARI-17909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398147#comment-15398147
]
Hudson commented on AMBARI-17909:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #5407 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5407/])
AMBARI-17909 AMS Storm Sink: apply change of Storm metrics improvement -
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7ff7bcf3a2d40693cb0a5881661236e07335973a])
*
ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java
*
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/storm-site.xml
*
ambari-metrics/ambari-metrics-storm-sink/src/test/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSinkTest.java
> AMS Storm Sink: apply change of Storm metrics improvement - worker level
> aggregation
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-17909
> URL: https://issues.apache.org/jira/browse/AMBARI-17909
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.4.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Blocker
> Attachments: AMBARI-17909-v1.patch, AMBARI-17909-v2.patch
>
>
> Abstraction:
> This issue is for following up changes on STORM-2006: Storm metrics feature
> improvement: support per-worker level metrics aggregation.
> Details:
> With recent patches for AMS and AMS Storm sink, AMS stores task level metrics
> from Storm, and relevant dashboards can be configured via Grafana.
> But we found that it incurs too many kinds of metrics and also too many data
> points published to AMS because even a topology can have lots of tasks.
> In order to reduce this, I addressed STORM-2006, but it also needs AMS Storm
> sink and relevant Storm configurations to be changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
