ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aravindan Vijayan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13585) Flume metrics do not match up with data being processed by storm
Date Thu, 10 Dec 2015 22:09:11 GMT

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

Aravindan Vijayan updated AMBARI-13585:
---------------------------------------
    Attachment: AMBARI-13585.patch

> 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.2.0
>
>         Attachments: AMBARI-13585.patch
>
>
> 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)

Mime
View raw message