[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-users
Subject:    Re: [Artemis] Detect slow consumers stop being slow
From:       Art Licis <arturs.licis () gmail ! com>
Date:       2017-11-23 16:56:14
Message-ID: CAK9nuG5KpkqMme6q1cqOpOasDg1tdOMJYuKMLdo=Jnt7W4j0nQ () mail ! gmail ! com
[Download RAW message or body]


Thanks for the clarification. I'll do the necessary research and,
hopefully, come up with a proposal as a PR.

- Art

On Thu, Nov 23, 2017 at 5:18 PM, Justin Bertram <jbertram@redhat.com> wrote:

> The core management API is exposed over JMX so they're essentially exactly
> the same.  As far as I know the documentation for the slow-consumer
> detection is up to date (which only describes the notification I believe).
> Feel free to send a pull-request for a per-consumer attribute, etc.  There
> is an issue open regarding how the slow-consumer detection actually works,
> but nothing regarding the functionality you're looking for.
>
>
> Justin
>
> On Wed, Nov 22, 2017 at 6:15 AM, art.licis <arturs.licis@gmail.com> wrote:
>
> > Dear community,
> >
> > I already have health monitor for ActiveMQ 5.x, and trying to do similar
> > for
> > Artemis. One of the main features is to notify when there's a slow
> > consumer,
> > and also notify when a consumer stops being slow consumer.
> >
> > For 5.x, I used JMX to query for SlowConsumer=true properties (if anyone
> > interested, it's on a github:
> > https://github.com/art-licis/activemq-jmx-monitor). I know I could use
> > notifications, but I needed JMX anyway to update list of outstanding slow
> > consumers and detect when they are not slow anymore.
> >
> > Now, there's a question on how I do it with Artemis? I can only detect
> slow
> > consumer using notification queue (_AMQ_NotifType: CONSUMER_SLOW), and I
> > couldn't find per-consumer status when browsing through JMX. Anything
> else
> > I'm missing or I could use for this? (NB: I also looked into Core
> > Management
> > API, but it looks pretty much the same as JMX).
> >
> > So any advice or hints are appreciated. Also, if there's any related
> > development backlog for this, I'd be very happy to contribute, just let
> me
> > know,- I'm studying sources atm and trying to identify the first issues
> to
> > start working on.
> >
> > Best,
> > Art
> >
> >
> >
> > --
> > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> > f2341805.html
> >
>


[prev in list] [next in list] [prev in thread] [next in thread]