[
https://issues.apache.org/jira/browse/QPID-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571340#action_12571340
]
Gordon Sim commented on QPID-801:
---------------------------------
Do we want a per-queue timestamp to measure latency or is per-message
sufficient? For per-queue the timestamp should be attached to QueuedMessage
(annoyingly still defined in Consumer.h). For per-message we could set it after
its been enqueued on all queues (as the patch stands it will be overwritten by
each queue its enqueued onto anyway); might be clearer. (Aside:
DeliveryProperties has a timestamp property, but I suspect that may not be of
sufficient granularity to what we need).
> Queue latency statistics added
> ------------------------------
>
> Key: QPID-801
> URL: https://issues.apache.org/jira/browse/QPID-801
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Reporter: Ted Ross
> Priority: Minor
> Attachments: qpid-patch24.diff
>
>
> The attached patch does two things:
> 1) Introduces a new management type: min/max/average time (in nSec)
> 2) Uses the new type to report queue latency (i.e. the min/max/average time a
> message stays in the queue)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
