[
https://issues.apache.org/jira/browse/CAMEL-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben O'Day updated CAMEL-1902:
-----------------------------
Attachment: camel-core-throughputLogger-groupPeriod.txt
here is a pass at this...
-first, I left support for "groupSize" (should this be removed entirely or
still supported??)
-added a new attribute called "groupPeriod", which can be used instead of
"groupSize"
-once the "groupPeriod" time is exceeded, the throughput stats are logged
By design, this won't report until a message has been received and won't report
during inactive periods (its not triggered by a timer, but checks the duration
since last log each time a message is received). I'd describe the
"groupPeriod" as a hint of when to log as it won't be exact, but under heavy
load (where these stats are useful, it should be within an acceptable range,
etc)....
Anyways, let me know if this approach works, otherwise I can try to use a timer
thread of some sort instead...
> 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
> Priority: Minor
> Fix For: 2.7.0
>
> Attachments: camel-core-throughputLogger-groupPeriod.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.
