Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 27 Oct 2015 21:08:27 +0000 (UTC)
From: "Siddharth Wagle (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12908298.1445965337000.76357.1445980107748@Atlassian.JIRA>
In-Reply-To: <JIRA.12908298.1445965337000@Atlassian.JIRA>
References: <JIRA.12908298.1445965337000@Atlassian.JIRA>
 <JIRA.12908298.1445965337200@arcas>
Subject: [jira] [Resolved] (AMBARI-13585) Flume metrics do not match up with
 data being processed by storm
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Siddharth Wagle resolved AMBARI-13585.
--------------------------------------
    Resolution: Fixed

Pushed to 2.1 and trunk.

> Flume metrics do not match up with data being processed by storm
> ----------------------------------------------------------------
>
>                 Key: AMBARI-13585
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13585
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.1.2
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.1.3
>
>
> Bug 
> Flume Metrics shown in the flume summary page of Ambari have very small values when correlated with the events being generated by the flume agents. This is because the flume metrics returned by AMS are "per millisecond" instead of "per second"
> Fix
> Since flume metrics are "rate" metrics, they have to divided by the time period in seconds rather than milliseconds to show them as "per sec" value in the charts.


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