Life With Zenoss Cloud Gives You Intelligent Insights
EXPLORE THE PLATFORM
Life With Zenoss Cloud Gives You ControlPrevent IT Outages and Predict Issues
Life With Zenoss Cloud Gives You Massive Scale
Zenoss Partner Portal
Become a Partner
Learn. Discuss. Participate.Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Customer Support Portal
Zenoss Learning Center
Analyst ReportForrester: Top 5 Focus Areas to Succeed With DevOps
Customers for LifeAt Zenoss, our customers are at the core of everything we do.
Request A Demo
This ZenPack is developed by the Zenoss user community and supported via our online forums. Zenoss, Inc. does not provide direct support for this ZenPack.
This Monitoring Zenpack provides monitoring of MQ Managers, Channels, and Queues for IBM Websphere MQ.
No agent is needed on the remote server.
Support for Windows and Unix-based platforms
Provides component-level modeling of the IBM MQ application components.
This ZenPack was inspired by the "IBM Websphere MQ ZenPack", and I'm grateful to its author for sharing some of his expertise regarding MQ.
I have been using a shell script to monitor specific MQ Queues on Windows/Unix servers for a couple of years. The good thing about the script is that it requires minimal support to run against Windows and Unix servers. The bad part is that all of the MQ-specific paramters (Manager, Queue) have to be supplied to it. It is also a pain to use to monitor multiple queues on a single machine, as new command definitions have to be made on a locally bound template that differ only in the command line options. A component-based template provides a much better solution, while the modelling scripts remove the need to keep track of the needed parameters.
The ZenPack has the following Device Class(es)
/Server/Linux/MQ, /Server/Windows/MQ Device Classes
MQManager Template provides:
Manager Status (Min/Max)
MQQueue Template provides:
Queue Depth (Min/Max)
MQChannel Template provides:
Common (shared class--do not use as a plugin)
After installing this Zenpack as usual, ensure that the authentication zProperties are set for Windows and Unix-based servers respectively.
SSH requires username/password, assumes mqm is the MQ user.
WINEXE on later Windows versions (2003(?) and up) may fail with an error similar to "problem installing winexesvc". This can be corrected by running the following commands from the Command Prompt (on the Windows server):
sc create winexesvc binPath= WINEXESVC.EXE start= auto DisplayName=
sc description winexesvc "Remote command provider for Zenoss
View the discussion thread.
This ZenPack is developed and supported by the Zenoss User Community. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Community ZenPacks.