You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/23 19:52:49 UTC
[jira] [Resolved] (QPID-3824) Additional queue statistics, posix
memory statistics, and broker-scope statistics
[ https://issues.apache.org/jira/browse/QPID-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross resolved QPID-3824.
----------------------------
Resolution: Fixed
> Additional queue statistics, posix memory statistics, and broker-scope statistics
> ---------------------------------------------------------------------------------
>
> Key: QPID-3824
> URL: https://issues.apache.org/jira/browse/QPID-3824
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, Python Tools
> Reporter: Ted Ross
> Assignee: Ted Ross
> Fix For: 0.15
>
>
> This feature introduces new counters to the Queue and Broker management objects. The broker counters are aggregate values of all queues in the broker.
> * = Already in the management model
> ||Counter||Queue||Broker||Description||
> |queueCount| |X|The number of queues on the broker|
> |msgTotalEnqueues, byteTotalEnqueues|*|X|Total Enqueues (messages, bytes)|
> |msgTotalDequeues, byteTotalDequeues|*|X|Total Dequeues (messages, bytes) This does not count messages acquired but not completed.|
> |msgDepth, byteDepth|*|X|Total mesages, bytes in the broker|
> |msgPersistEnqueues, bytePersistEnqueues|*|X|Durable messages/bytes enqueued into durable queues|
> |msgPersistDequeues, bytePersistDequeues|*|X|Durable messages/bytes dequeued from durable queues|
> |msgTxnEnqueues, byteTxnEnqueues|*|X|Transactional enqueues in messages/bytes|
> |msgTxnDequeues, byteTxnDequeues|*|X|Transactional dequeues in messages/bytes|
> |msgFtdEnqueues, byteFtdEnqueues|X|X|Messages/bytes flowed to disk (released from memory)|
> |msgFtdDequeues, byteFtdDequeues|X|X|Messages/bytes recovered from disk for consumption|
> |msgFtdDepth, byteFtdDepth|X|X|Messages/bytes currently flowed to disk|
> |releases|X|X|Total messages released from acquired state (explicitly by API or due to subscriber deletion)|
> |acquires|X|X|Total messages acquired|
> |discardsNoRoute| |X|Messages discarded due to no-route from exchange|
> |discardsTtl|X|X|Messages discarded due to TTL expiration|
> |discardsRing|X|X|Messages discarded on full ring queue|
> |discardsLvq|X|X|Messages discarded from LVQ due to key match|
> |discardsOverflow|X|X|Messages discarded due to limit exceeded (sender exception thrown)|
> |discardsSubscriber|X|X|Messages rejected by subscriber|
> |discardsPurge|X|X|Messages purged by management request|
> |reroutes|X|X|Messages rerouted by management request|
> |abandoned| |X|Messages abandoned in deleted queues|
> |abandonedViaAlt| |X|Messages routed to alternate exchange in deleted queues|
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org