You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "James A. Robinson" <ji...@highwire.org> on 2015/07/23 19:39:17 UTC
Monitoring?
What tools do you folks find to be effective for monitoring the health of
your brokers?
I see several nagios plugins do things like check queue depth. I also note
that most of the plugins I see have no concept of monitoring a failover
capable cluster.
Jim
Re: Monitoring?
Posted by "James A. Robinson" <ji...@highwire.org>.
Hi,
You're talking about http://rhq-project.github.io/rhq/?
On Fri, Jul 24, 2015 at 11:42 AM <ba...@wellsfargo.com> wrote:
> RHQ is a great tool to use to monitor brokers and queues/topics.
>
RE: Monitoring?
Posted by ba...@wellsfargo.com.
RHQ is a great tool to use to monitor brokers and queues/topics.
Regards,
Barry
-----Original Message-----
From: burtonator2011@gmail.com [mailto:burtonator2011@gmail.com] On Behalf Of Kevin Burton
Sent: Friday, July 24, 2015 2:32 PM
To: users@activemq.apache.org
Subject: Re: Monitoring?
I really wish ActiveMQ had integrated support for jolokia :)
On Thu, Jul 23, 2015 at 9:24 PM, Tim Bain <tb...@alumni.duke.edu> wrote:
> That frequency will be much better.
>
> And I think the RESTful API is supposed to be faster if you're doing
> queries in bulk, because JMX isn't bad within the JVM, it's just slow
> when you have to use RPC across a network. But I haven't done it
> myself, so I can't comment on it first-hand.
>
> Tim
>
> On Thu, Jul 23, 2015 at 10:11 PM, James A. Robinson
> <ji...@highwire.org>
> wrote:
>
> > I was thinking more like every five minutes. Is it equally expensive
> > to query via the restful api?
> > On Thu, Jul 23, 2015 at 21:07 Tim Bain <tb...@alumni.duke.edu> wrote:
> >
> > > Keep in mind that remote JMX calls are pretty expensive even on a
> > > local network, so you'll have to either not monitor all that much
> > > stuff or
> not
> > > retrieve values super often. As with everything related to
> performance,
> > > YMMV so plan to measure how much throughput you can actually do,
> > > but
> > don't
> > > expect to get all stats for all destinations and clients every 100ms.
> > > On Jul 23, 2015 1:52 PM, "James A. Robinson" <ji...@highwire.org>
> wrote:
> > >
> > > > Thank you. I'll explore using nagios check_jmx to query the
> > > > activemq MBeans.
> > > >
> > > > Jim
> > > >
> > > >
> > > > On Thu, Jul 23, 2015 at 11:48 AM Tim Bain
> > > > <tb...@alumni.duke.edu>
> > wrote:
> > > >
> > > > > I've used primitive log-monitoring tools such as Swatch to
> > > > > notify
> us
> > > when
> > > > > producer flow control kicked in or when a consumer became slow
> > > > > and
> > was
> > > > > aborted, because those were both situations we were concerned
> about.
> > > > I've
> > > > > also written Java code to interrogate the JMX stats for
> > > > > specific destinations and log them regularly, so I could do
> > > > > forensics later
> > > about
> > > > > what backed up and hopefully figure out why.
> > > > >
> > > > > Tim
> > > > >
> > > > > On Thu, Jul 23, 2015 at 11:39 AM, James A. Robinson <
> > jimr@highwire.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > What tools do you folks find to be effective for monitoring
> > > > > > the
> > > health
> > > > of
> > > > > > your brokers?
> > > > > >
> > > > > > I see several nagios plugins do things like check queue
> > > > > > depth. I
> > > also
> > > > > note
> > > > > > that most of the plugins I see have no concept of monitoring
> > > > > > a
> > > failover
> > > > > > capable cluster.
> > > > > >
> > > > > > Jim
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>
Re: Monitoring?
Posted by Kevin Burton <bu...@spinn3r.com>.
I really wish ActiveMQ had integrated support for jolokia :)
On Thu, Jul 23, 2015 at 9:24 PM, Tim Bain <tb...@alumni.duke.edu> wrote:
> That frequency will be much better.
>
> And I think the RESTful API is supposed to be faster if you're doing
> queries in bulk, because JMX isn't bad within the JVM, it's just slow when
> you have to use RPC across a network. But I haven't done it myself, so I
> can't comment on it first-hand.
>
> Tim
>
> On Thu, Jul 23, 2015 at 10:11 PM, James A. Robinson <ji...@highwire.org>
> wrote:
>
> > I was thinking more like every five minutes. Is it equally expensive to
> > query via the restful api?
> > On Thu, Jul 23, 2015 at 21:07 Tim Bain <tb...@alumni.duke.edu> wrote:
> >
> > > Keep in mind that remote JMX calls are pretty expensive even on a local
> > > network, so you'll have to either not monitor all that much stuff or
> not
> > > retrieve values super often. As with everything related to
> performance,
> > > YMMV so plan to measure how much throughput you can actually do, but
> > don't
> > > expect to get all stats for all destinations and clients every 100ms.
> > > On Jul 23, 2015 1:52 PM, "James A. Robinson" <ji...@highwire.org>
> wrote:
> > >
> > > > Thank you. I'll explore using nagios check_jmx to query the activemq
> > > > MBeans.
> > > >
> > > > Jim
> > > >
> > > >
> > > > On Thu, Jul 23, 2015 at 11:48 AM Tim Bain <tb...@alumni.duke.edu>
> > wrote:
> > > >
> > > > > I've used primitive log-monitoring tools such as Swatch to notify
> us
> > > when
> > > > > producer flow control kicked in or when a consumer became slow and
> > was
> > > > > aborted, because those were both situations we were concerned
> about.
> > > > I've
> > > > > also written Java code to interrogate the JMX stats for specific
> > > > > destinations and log them regularly, so I could do forensics later
> > > about
> > > > > what backed up and hopefully figure out why.
> > > > >
> > > > > Tim
> > > > >
> > > > > On Thu, Jul 23, 2015 at 11:39 AM, James A. Robinson <
> > jimr@highwire.org
> > > >
> > > > > wrote:
> > > > >
> > > > > > What tools do you folks find to be effective for monitoring the
> > > health
> > > > of
> > > > > > your brokers?
> > > > > >
> > > > > > I see several nagios plugins do things like check queue depth. I
> > > also
> > > > > note
> > > > > > that most of the plugins I see have no concept of monitoring a
> > > failover
> > > > > > capable cluster.
> > > > > >
> > > > > > Jim
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>
Re: Monitoring?
Posted by Tim Bain <tb...@alumni.duke.edu>.
That frequency will be much better.
And I think the RESTful API is supposed to be faster if you're doing
queries in bulk, because JMX isn't bad within the JVM, it's just slow when
you have to use RPC across a network. But I haven't done it myself, so I
can't comment on it first-hand.
Tim
On Thu, Jul 23, 2015 at 10:11 PM, James A. Robinson <ji...@highwire.org>
wrote:
> I was thinking more like every five minutes. Is it equally expensive to
> query via the restful api?
> On Thu, Jul 23, 2015 at 21:07 Tim Bain <tb...@alumni.duke.edu> wrote:
>
> > Keep in mind that remote JMX calls are pretty expensive even on a local
> > network, so you'll have to either not monitor all that much stuff or not
> > retrieve values super often. As with everything related to performance,
> > YMMV so plan to measure how much throughput you can actually do, but
> don't
> > expect to get all stats for all destinations and clients every 100ms.
> > On Jul 23, 2015 1:52 PM, "James A. Robinson" <ji...@highwire.org> wrote:
> >
> > > Thank you. I'll explore using nagios check_jmx to query the activemq
> > > MBeans.
> > >
> > > Jim
> > >
> > >
> > > On Thu, Jul 23, 2015 at 11:48 AM Tim Bain <tb...@alumni.duke.edu>
> wrote:
> > >
> > > > I've used primitive log-monitoring tools such as Swatch to notify us
> > when
> > > > producer flow control kicked in or when a consumer became slow and
> was
> > > > aborted, because those were both situations we were concerned about.
> > > I've
> > > > also written Java code to interrogate the JMX stats for specific
> > > > destinations and log them regularly, so I could do forensics later
> > about
> > > > what backed up and hopefully figure out why.
> > > >
> > > > Tim
> > > >
> > > > On Thu, Jul 23, 2015 at 11:39 AM, James A. Robinson <
> jimr@highwire.org
> > >
> > > > wrote:
> > > >
> > > > > What tools do you folks find to be effective for monitoring the
> > health
> > > of
> > > > > your brokers?
> > > > >
> > > > > I see several nagios plugins do things like check queue depth. I
> > also
> > > > note
> > > > > that most of the plugins I see have no concept of monitoring a
> > failover
> > > > > capable cluster.
> > > > >
> > > > > Jim
> > > > >
> > > >
> > >
> >
>
Re: Monitoring?
Posted by "James A. Robinson" <ji...@highwire.org>.
I was thinking more like every five minutes. Is it equally expensive to
query via the restful api?
On Thu, Jul 23, 2015 at 21:07 Tim Bain <tb...@alumni.duke.edu> wrote:
> Keep in mind that remote JMX calls are pretty expensive even on a local
> network, so you'll have to either not monitor all that much stuff or not
> retrieve values super often. As with everything related to performance,
> YMMV so plan to measure how much throughput you can actually do, but don't
> expect to get all stats for all destinations and clients every 100ms.
> On Jul 23, 2015 1:52 PM, "James A. Robinson" <ji...@highwire.org> wrote:
>
> > Thank you. I'll explore using nagios check_jmx to query the activemq
> > MBeans.
> >
> > Jim
> >
> >
> > On Thu, Jul 23, 2015 at 11:48 AM Tim Bain <tb...@alumni.duke.edu> wrote:
> >
> > > I've used primitive log-monitoring tools such as Swatch to notify us
> when
> > > producer flow control kicked in or when a consumer became slow and was
> > > aborted, because those were both situations we were concerned about.
> > I've
> > > also written Java code to interrogate the JMX stats for specific
> > > destinations and log them regularly, so I could do forensics later
> about
> > > what backed up and hopefully figure out why.
> > >
> > > Tim
> > >
> > > On Thu, Jul 23, 2015 at 11:39 AM, James A. Robinson <jimr@highwire.org
> >
> > > wrote:
> > >
> > > > What tools do you folks find to be effective for monitoring the
> health
> > of
> > > > your brokers?
> > > >
> > > > I see several nagios plugins do things like check queue depth. I
> also
> > > note
> > > > that most of the plugins I see have no concept of monitoring a
> failover
> > > > capable cluster.
> > > >
> > > > Jim
> > > >
> > >
> >
>
Re: Monitoring?
Posted by Tim Bain <tb...@alumni.duke.edu>.
Keep in mind that remote JMX calls are pretty expensive even on a local
network, so you'll have to either not monitor all that much stuff or not
retrieve values super often. As with everything related to performance,
YMMV so plan to measure how much throughput you can actually do, but don't
expect to get all stats for all destinations and clients every 100ms.
On Jul 23, 2015 1:52 PM, "James A. Robinson" <ji...@highwire.org> wrote:
> Thank you. I'll explore using nagios check_jmx to query the activemq
> MBeans.
>
> Jim
>
>
> On Thu, Jul 23, 2015 at 11:48 AM Tim Bain <tb...@alumni.duke.edu> wrote:
>
> > I've used primitive log-monitoring tools such as Swatch to notify us when
> > producer flow control kicked in or when a consumer became slow and was
> > aborted, because those were both situations we were concerned about.
> I've
> > also written Java code to interrogate the JMX stats for specific
> > destinations and log them regularly, so I could do forensics later about
> > what backed up and hopefully figure out why.
> >
> > Tim
> >
> > On Thu, Jul 23, 2015 at 11:39 AM, James A. Robinson <ji...@highwire.org>
> > wrote:
> >
> > > What tools do you folks find to be effective for monitoring the health
> of
> > > your brokers?
> > >
> > > I see several nagios plugins do things like check queue depth. I also
> > note
> > > that most of the plugins I see have no concept of monitoring a failover
> > > capable cluster.
> > >
> > > Jim
> > >
> >
>
Re: Monitoring?
Posted by "James A. Robinson" <ji...@highwire.org>.
Thank you. I'll explore using nagios check_jmx to query the activemq
MBeans.
Jim
On Thu, Jul 23, 2015 at 11:48 AM Tim Bain <tb...@alumni.duke.edu> wrote:
> I've used primitive log-monitoring tools such as Swatch to notify us when
> producer flow control kicked in or when a consumer became slow and was
> aborted, because those were both situations we were concerned about. I've
> also written Java code to interrogate the JMX stats for specific
> destinations and log them regularly, so I could do forensics later about
> what backed up and hopefully figure out why.
>
> Tim
>
> On Thu, Jul 23, 2015 at 11:39 AM, James A. Robinson <ji...@highwire.org>
> wrote:
>
> > What tools do you folks find to be effective for monitoring the health of
> > your brokers?
> >
> > I see several nagios plugins do things like check queue depth. I also
> note
> > that most of the plugins I see have no concept of monitoring a failover
> > capable cluster.
> >
> > Jim
> >
>
Re: Monitoring?
Posted by Tim Bain <tb...@alumni.duke.edu>.
I've used primitive log-monitoring tools such as Swatch to notify us when
producer flow control kicked in or when a consumer became slow and was
aborted, because those were both situations we were concerned about. I've
also written Java code to interrogate the JMX stats for specific
destinations and log them regularly, so I could do forensics later about
what backed up and hopefully figure out why.
Tim
On Thu, Jul 23, 2015 at 11:39 AM, James A. Robinson <ji...@highwire.org>
wrote:
> What tools do you folks find to be effective for monitoring the health of
> your brokers?
>
> I see several nagios plugins do things like check queue depth. I also note
> that most of the plugins I see have no concept of monitoring a failover
> capable cluster.
>
> Jim
>