[jira] [Resolved] (ARTEMIS-418) Add more queue-level attributes to improve JMX-based monitoring

["Justin Bertram (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-418.
------------------------------------
    Resolution: Incomplete

Need a clear explanation of what MinMessageSize, AverageMessageSize, MaxMessageSize actually measure, and how these metrics correspond (or not) to those in ActiveMQ 5.x with the same name.

> 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)