Count me in the roll-your-own column. I can't justify any $$ for a real monitor yet, so mine just sends messages from the hub to all the spokes and waits for COA replies. If it doesn't get one, it e-mails people. I've got a list of enhancements I'd like to make....
Bill -----Original Message----- From: Mabrito, Greg [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 9:46 AM To: [EMAIL PROTECTED] Subject: MQ monitoring questions I am trying to get a feel for how many MQers out there have written their own monitoring apps. With the APIs and Administrative Interfaces that come with MQ it has been pretty easy to write our own monitoring/performance data collecting agents that run outside the QMgr. Sure they are not as complex and might not offer all the bells and whistles (and no end to end message tracking which would be really cool) that the vendors offer but our own apps actually work, are reliable, and capture lots of different stats on many types of MQ objects. After two years and two failed vendors we finally took this route. If you could just let me know who out there is running their own home grown monitoring/performance apps instead of relying on vendor solutions. Thanks, Greg The opinions herein are solely Greg's and are not necessarily the opinion of USAA. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
