[
https://issues.apache.org/jira/browse/FLUME-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454554#comment-13454554
]
Ted Malaska commented on FLUME-1411:
------------------------------------
I can do what you ask. But let me clarify and ask one more question.
1. Clarify
When I said getAverage(String counter) in MonitoredCounterGroup it is like
- getAverage(COUNTER_EVENT_TAKE_ATTEMPT) is to getAverageEventRate() as
get(COUNTER_EVENT_TAKE_ATTEMPT) getEventTakeAttemptCount.
So on that note, we are saying the same thing. :)
2. Question
When you say "averages events/sec since the component started" it is a simple a
dividing the number of events by the number of second since the component
started.
The problem with that approach is the longer the component runs the less
reactive the result of getAverage will be to changes to events per second. So
the value becomes less valuable to the user the longer the component runs.
What would be really cool if the user could get like the average for the last N
minutes and chart it in something like
http://mbostock.github.com/d3/ex/stack.html
The reset is one way to do this. Another way to do this is change the method
to say something like getLastMinuteAverageOfFoo()
Do you see what I saying?
> Add average events per second params to MBeans
> ----------------------------------------------
>
> Key: FLUME-1411
> URL: https://issues.apache.org/jira/browse/FLUME-1411
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.2.0
> Reporter: Hari Shreedharan
> Fix For: v1.3.0
>
>
> I know this might cause the platform mbean thread longer to poll, since we
> will need to do some calculation - but it is definitely nice to have historic
> averages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
