You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2016/07/27 01:48:20 UTC

[jira] [Updated] (AMBARI-17909) AMS Storm Sink: apply change of Storm metrics improvement - worker level aggregation

     [ https://issues.apache.org/jira/browse/AMBARI-17909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jungtaek Lim updated AMBARI-17909:
----------------------------------
    Attachment: AMBARI-17909-v1.patch

> 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
>
>
> 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)