As Rob mentioned, people tend to use the JMX interface and/or log scraping with the Java broker. There are ways to get most/all of the information thats logged from the JMX interface as well (plus a lot more) its just sometimes its a little convoluted to do so, eg message age would involve inspecting the headers of a message whereas it is just logged when the threshold is exceeded. Depending on what you want to do, I would expect 3) and 1) to be the quickest and easiest. As Rob mentioned, 2) will likely be hit or miss as the Java brokers QMF implementation is incomplete and not well tested with the tooling used for the C++ broker.
We currently have our own Eclipse RCP based JMX management console for the Java broker, but are looking to retire it and bring in HTTP based management with a web UI later in the year (in addition to the JMX interface). You are however free to use any JMX tools of your choice with the broker (JConsole, VisualVM, Nagios, etc etc) and as far as I know Nagios already has some JMX plugins available for it so even if you wanted to write a custom one you should have those as a basis point. Robbie On 16 May 2012 19: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]
