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" <j...@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 <j...@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 > > > > > > > > > >
