Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
check_mq IBM WebSphere MQSeries Queues Monitor
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
java program that check the depth of a queue.
does not require MQ client!
1) copy the file to your nagios libexec directory.
2) define a command at checkcommands.cfg:
define command{
command_name check_mq
command_line java -jar $USER1$/mq-utils.jar $ARG1$ $ARG2$ $HOSTADDRESS$ $ARG3$ $ARG4$ -w $ARG5$ -c $ARG6$ -debug
}
3) the service check command should be:
check_command check_mq!QMGR!PORT#!CHANNEL!QUEUENAME!WARNING#!CRITICAL#
does not require MQ client!
1) copy the file to your nagios libexec directory.
2) define a command at checkcommands.cfg:
define command{
command_name check_mq
command_line java -jar $USER1$/mq-utils.jar $ARG1$ $ARG2$ $HOSTADDRESS$ $ARG3$ $ARG4$ -w $ARG5$ -c $ARG6$ -debug
}
3) the service check command should be:
check_command check_mq!QMGR!PORT#!CHANNEL!QUEUENAME!WARNING#!CRITICAL#
Reviews (6)
byjajohnso77, July 23, 2020
Back in 2013, I found this service check and I started to use it. Almost immediately the MQ admins started yelling at me for causing a ton of errors in their logs because the service check wasn't properly closing out from the queue / queue manager and simply disconnecting which was a no-no. I was annoyed and embarrassed so I tried finding the source code somewhere online but I couldn't. So, I found a java decompiler and decided to try and decompile and fix what I could.
I was able to get this working properly with a lot of google. I had always meant to put this up in github but I never got around to it until this week. I found the source code and compiled jar and I'm making it available.
I am not the original author of this service check and I'm not affiliated with Traiana. I just fixed a buggy MQ API call.
https://github.com/JJinMaine/nagios-mq-checks
YMMV
I was able to get this working properly with a lot of google. I had always meant to put this up in github but I never got around to it until this week. I found the source code and compiled jar and I'm making it available.
I am not the original author of this service check and I'm not affiliated with Traiana. I just fixed a buggy MQ API call.
https://github.com/JJinMaine/nagios-mq-checks
YMMV
bymokeefe, December 16, 2014
This plugin is not currently under development. If you would like to take the lead on this project email sales@nagios.com
bysbergonzi, April 2, 2014
easy install, all i needed was the queue depth and alert if greater than the parameters.
should the graph display? that is show times where the depth was > 0? messages clear quickly, though if something is wrong it would spike.
should the graph display? that is show times where the depth was > 0? messages clear quickly, though if something is wrong it would spike.
bypatr, June 14, 2013
The Warning and Critical value is the depth of the queue or better said the number of messages that are present in the queue. so having more messages in the queue then the warning will give you a warning. Same for Critical.
so putting Warning on 2 and Critical on 4. Then you will get a warning if you have 2 messages in the queue and a critical warning if you have 4 messages in the queue.
so putting Warning on 2 and Critical on 4. Then you will get a warning if you have 2 messages in the queue and a critical warning if you have 4 messages in the queue.
bysujitt, April 11, 2013
Does the command line below have to have the Exclamation mark and what are all the ARGs for a little documentation would be great.
thanks keep up the goodwork
thanks keep up the goodwork
from MQ logs:
......................
CSQX599E WBGE CSQXRESP Channel CLIENT.TO.CSQ1 ended abnormally CSQX209E CSQ1 CSQXRESP Connection unexpectedly terminated, channel CLIENT.TO.CSQ1, connection nagios (XX.XX.XX.XX) (queue manager ????) TRPTYPE=TCP
..............
Pheraps it would be better to close the connection at the end of any check ?
A good plugin. I found it very useful. Thanks a lot.
......................
CSQX599E WBGE CSQXRESP Channel CLIENT.TO.CSQ1 ended abnormally CSQX209E CSQ1 CSQXRESP Connection unexpectedly terminated, channel CLIENT.TO.CSQ1, connection nagios (XX.XX.XX.XX) (queue manager ????) TRPTYPE=TCP
..............
Pheraps it would be better to close the connection at the end of any check ?
A good plugin. I found it very useful. Thanks a lot.
