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

ASF GitHub Bot commented on ARTEMIS-1433:
-----------------------------------------

GitHub user pgfox opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1549

    ARTEMIS-1433 adding AddressMemoryUsage()/AddressMemoryUsagePercentage() 

    
    expose the total amount of memory used by the Addresses on the broker and 
express it as a percentage of the global-max-size limit. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/pgfox/activemq-artemis memory_used

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1549.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 #1549
    
----
commit 4f0a7067beac484c41b4ae5a59532115124cbe04
Author: Pat Fox <[email protected]>
Date:   2017-09-22T08:54:07Z

    ARTEMIS-1433 adding AddressMemoryUsage() and AddressMemoryUsagePercentage() 
to ActiveMQServerControl

----


> expose total Address memory usage in JMX
> ----------------------------------------
>
>                 Key: ARTEMIS-1433
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1433
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.3.0
>            Reporter: Pat Fox
>            Priority: Minor
>
> activemq 5.x had a MemoryPercentUsage attribute exposed on the broker MBean 
> which showed how much memory was being used by the broker destinations, as a 
> percentage of the overall memory.
> Although the memory model in Artemis is different, I think it would still be 
> useful to see how much memory the addresses are using in total and also have 
> it expressed as a percentage of the global-max-size.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to