[
https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43276#action_43276
]
Claus Ibsen commented on CAMEL-578:
-----------------------------------
William.
At first glance the nano second timing value doesn't give me good indication if
the elapsed time is fast or not - we are so used to milli seconds.
Can you create a patch that uses millis instead?
And I do think the text in the jconsole should display the unit of the timing
MinProcessingTime [millis]
MeanProcessingTime [millis]
MaxProcessingTime [millis]
> JMX Instrumentation - PerformanceCounter - last processed timestamp
> -------------------------------------------------------------------
>
> Key: CAMEL-578
> URL: https://issues.apache.org/activemq/browse/CAMEL-578
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.3.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 1.4.0
>
> Attachments: jconsole.PNG, jconsole_nanosecond.PNG,
> nanosecnd-patch.txt, patch.txt
>
>
> Add a timestamp for the last completed exchange on the Camel JMX
> PerfformanceCounter.
> Its very nice to be able to see this information in the JMX console.
> And maybe add a first processed timestamp as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
