Sorry. I should have said I wish to use the Java broker. Did you write a custom JMX tool?
On 16 May 2012 16:47, Rob Godfrey <[email protected]> wrote: > I'm not sure from your question whether you are talking of the Java or > C++ Broker. > > We use the Java Broker in-house and use a mixture of log scraping and > JMX. The Java Broker's QMF support need a bit of an overhaul and > probably doesn't work with all of the QMF toolset at the moment. > > For the C++ Broker QMF is obviously an option, along with the logging, > as you mentioned. I don't think the QMF-JMX bridge is maintained > anymore and I believe we no longer release it. > > -- Rob > > On 16 May 2012 20:29, oggie <[email protected]> wrote: > > While evaluating QPid, I also need to determine if it can be monitored > > easily. Our current monitoring tool is nagios. > > > > We need to be able to monitor the queue for things such as: > > 1 - empty queue > > 2 - full queue > > 3 - old messages > > 4 - slowness > > etc. > > > > As far as I can tell, there's three options: > > 1 - Add the startup option to have qpid write to the system log and then > > just get nagios to montor that log > > 2 - Use QMF and write a nagios plugin in python to use QMF. > > 3 - Write a jmx client plugin for nagios that uses the jmx interface in > > qpid. > > > > Does anyone have any experience with this? Anything they'd like to > share? Is > > one option better than the others? > > > > I think the #1 and #2 would be the quickest to implement. > > > > Thanks! > > > > > > -- > > View this message in context: > http://qpid.2158936.n2.nabble.com/monitoring-and-alarms-alerts-tp7562412.html > > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
