activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-417) Add more broker-level attributes to improve JMX-based monitoring
Date Wed, 20 Apr 2016 03:01:25 GMT


ASF subversion and git services commented on ARTEMIS-417:

Commit 9d7a49b38812d28e7a1e8fe9a5cae62ad1e3b96b in activemq-artemis's branch refs/heads/master
from [~jbertram]
[;h=9d7a49b ]

ARTEMIS-417 more broker-level JMX attrs

> Add more broker-level attributes to improve JMX-based monitoring
> ----------------------------------------------------------------
>                 Key: ARTEMIS-417
>                 URL:
>             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

View raw message