Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 20 Apr 2016 03:01:25 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12941352.1456221646000.274390.1461121285544@Atlassian.JIRA>
In-Reply-To: <JIRA.12941352.1456221646000@Atlassian.JIRA>
References: <JIRA.12941352.1456221646000@Atlassian.JIRA>
 <JIRA.12941352.1456221646125@arcas>
Subject: [jira] [Commented] (ARTEMIS-417) Add more broker-level attributes
 to improve JMX-based monitoring
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ARTEMIS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249174#comment-15249174 ] 

ASF subversion and git services commented on ARTEMIS-417:
---------------------------------------------------------

Commit 9d7a49b38812d28e7a1e8fe9a5cae62ad1e3b96b in activemq-artemis's branch refs/heads/master from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=9d7a49b ]

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)