[
https://issues.apache.org/jira/browse/ARTEMIS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256869#comment-15256869
]
Justin Bertram commented on ARTEMIS-418:
----------------------------------------
Based on my perusal of the ActiveMQ 5.x code it looks like MinMessageSize,
AverageMessageSize, and MaxMessageSize are based on all the messages that have
been sent to the queue rather than the messages that are currently in the
queue. Is that correct? I couldn't find any documentation specifically
explaining these metrics.
> Add more queue-level attributes to improve JMX-based monitoring
> ---------------------------------------------------------------
>
> Key: ARTEMIS-418
> URL: https://issues.apache.org/jira/browse/ARTEMIS-418
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Lionel Cons
> Assignee: Justin Bertram
>
> Here are some queue level attributes, useful for monitoring purposes, exposed
> by ActiveMQ 5.x and not (yet) by Artemis.
> - message size stats: MinMessageSize, AverageMessageSize, MaxMessageSize
> - memory store usage: MemoryPercentUsage
> - number of messages expired from this queue: ExpiredCount
> Also, we need to get the total number of messages received/sent by/from the
> queue. This may be MessagesAdded (EnqueueCount in ActiveMQ) and
> MessagesAcknowledged (DequeueCount in ActiveMQ) but the Artemis attributes
> are not yet documented (see ARTEMIS-405)...
> See also ARTEMIS-417 for broker-level attributes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
