activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Burton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5624) Slow consumer count for broker/destination for monitoring purposes.
Date Sun, 01 Mar 2015 22:32:04 GMT

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

Kevin Burton commented on AMQ-5624:
-----------------------------------

Another reason why this is valuable is for unit tests.  This way you can easily verify that
your code is properly handling slow consumers and verify that slow consumers were detected.

> Slow consumer count for broker/destination for monitoring purposes.
> -------------------------------------------------------------------
>
>                 Key: AMQ-5624
>                 URL: https://issues.apache.org/jira/browse/AMQ-5624
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: Kevin Burton
>
> According to this:
> http://activemq.apache.org/jmx.html
> There are no simple metrics for the number of slow consumers.
> Is there an easy way to figure this out?
> Would be nice for monitoring systems so that alerts can be triggered.
> Right now you have to enumerate each subscriber but it takes 200ms for each one so it
could take a rather long time.
> Plus, it’s better to have something O(1) for monitoring systems vs something O(N) which
might take a rather long time.
> This might be helpful at the broker level but destination level too.
> We can get this information right now for consumers but it's slow to compute.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message