[
https://issues.apache.org/jira/browse/CAMEL-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977668#action_12977668
]
Claus Ibsen commented on CAMEL-1902:
------------------------------------
Thanks Ben.
The start/stop can be done by using a service. Check the source committed how
it was done.
trunk: 1055340.
I would like either to improve the current logging message to include number of
messages received since last log.
Currently we have
{code}
Received: 3 messages so far. Last group took: 310 millis which is: 9.677
messages per second. average: 9.677
Received: 7 messages so far. Last group took: 200 millis which is: 20 messages
per second. average: 13.725
{code}
1)
We should maybe skip the very first log as it would be faulty, eg it lasted 310
millis, where as the rate was 200 millis.
So we should move the starttime initialization to the very first trigger, and
then just skip logging that first time.
2)
Maybe the log message could be something like this. Notice that 4 new messages,
is the number of messages received since last log.
And we can still print the total messages as well.
{code}
Received: 4 new messages, with total 7 so far. Last group took: 200 millis
which is: 20 messages per second. average: 13.725
{code}
3)
The wiki page should be updated with the new options
http://camel.apache.org/log
> ThroughputLogger - Add ability to be timer based
> ------------------------------------------------
>
> Key: CAMEL-1902
> URL: https://issues.apache.org/jira/browse/CAMEL-1902
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.0-M3
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.6.0
>
> Attachments: camel-core-throughputLogger-groupInterval.txt
>
>
> The ThroughputLogger is based on a size so it reports when X messages has
> passed it.
> What is needed is to be able to say it should report every X period instead.
> And add option to not report before first message have arrived.
> And add option to not report if the value was 0 for the 2nd time in case of a
> long inactivity period
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
