You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/19 16:28:25 UTC
[jira] [Commented] (ARTEMIS-417) Add more broker-level attributes
to improve JMX-based monitoring
[ https://issues.apache.org/jira/browse/ARTEMIS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247839#comment-15247839 ]
ASF GitHub Bot commented on ARTEMIS-417:
----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/473
ARTEMIS-417 more broker-level JMX attrs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-417
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/473.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #473
----
commit 220b6c06fdba1e281c743642b646eaa56f8eb572
Author: jbertram <jb...@apache.org>
Date: 2016-04-15T23:56:00Z
ARTEMIS-417 more broker-level JMX attrs
----
> Add more broker-level attributes to improve JMX-based monitoring
> ----------------------------------------------------------------
>
> Key: ARTEMIS-417
> URL: https://issues.apache.org/jira/browse/ARTEMIS-417
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Reporter: Lionel Cons
> Assignee: Justin Bertram
>
> Here are some broker level attributes, useful for monitoring purposes, exposed by ActiveMQ 5.x and not (yet) by Artemis.
> - uptime: Uptime and UptimeMillis
> - total number of connections since start (to derive a rate): TotalConnectionsCount
> - total number of messages received (to derive a rate): TotalEnqueueCount
> - total number of messages sent (to derive a rate): TotalDequeueCount
> - number of messages currently in the broker: TotalMessageCount
> - current number of subscriptions/consumers: TotalConsumerCount
> - memory store usage: MemoryPercentUsage
> - disk store usage: TempPercentUsage and StorePercentUsage
> Some of these may be computed from other MBeans (one could sum all the MessageCount from all the queues) but this does not scale. With heavily used brokers (e.g. thousands of destinations or connections or subscriptions...), it is not really feasible to frequently iterate through many thousands MBeans just to get an aggregated total.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)