[
https://issues.apache.org/jira/browse/AMBARI-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977364#comment-14977364
]
Hudson commented on AMBARI-13585:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3725 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3725/])
AMBARI-13585. Flume metrics do not match up with data being processed by
(swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f342ea96015d717e6cda1d21134ce4f0e38d38fa])
*
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/HBaseTimelineMetricStore.java
> 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)
