xymon MQ monitoring
list Ross Bradley
Hi,
I am trying to use xymon to get a view on MQ queues and channels but am
not enjoying any success. Here's my setup: -
Server
OS Centos 5.6
Xymon Server 4.3.3
Client
OS AIX 5300-9
Hobbit client 4.2.0-9
I have MQ version 6.0.2.8 running on the client.
Client-side; I seem to be okay. The client is sending information about
MQ to the xymon server. The data looks like: -
client/mqcollect ukclaqh01.mqcollect mqcollect
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager PCMS1.
1 : display qlocal(*) curdepth
AMQ8409: Display Queue details.
QUEUE(AMQ.MQEXPLORER.66061296) TYPE(QLOCAL)
CURDEPTH(0)
AMQ8409: Display Queue details.
QUEUE(CUSTOMER.CMSADDRESS.UPDATE.LQ) TYPE(QLOCAL)
CURDEPTH(0)
AMQ8409: Display Queue details.
QUEUE(CUSTOMER.CMSLEDGER.TRANSACTION.CREATE.LQ)
TYPE(QLOCAL) CURDEPTH(0)
...
...
...
AMQ8409: Display Queue details.
QUEUE(SYSTEM.PENDING.DATA.QUEUE) TYPE(QLOCAL)
CURDEPTH(0)
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
I've highlighted the first line as I think that this may be important.
At the xymon server I have added the following stanza to the
analysis.cfg file: -
HOST=ukclaqh01
# MQ_QUEUE CUSTOMER.*
MQ_QUEUE "CUSTOMER.CMSADDRESS.UPDATE.LQ"
MQ_QUEUE SYSTEM.CLUSTER.REPOSITORY.QUEUE [depth-warning=1]
MQ_CHANNEL *
But... no joy! Any help would be gratefully received.
Ross
Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151.
Express Gifts Limited is authorised and regulated by the Financial Services Authority
NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT helpdesk on +44(0) 1254 303030
list Ross Bradley
Hi,
I am trying to use xymon to get a view on MQ queues and channels but am not enjoying any success. Here’s my setup: -
Server
OS Centos 5.6
Xymon Server 4.3.3
Client
OS AIX 5300-9
Hobbit client 4.2.0-9
I have MQ version 6.0.2.8 running on the client. Client-side; I seem to be okay. The client is sending information about MQ to the xymon server. The data looks like: -
client/mqcollect ukclaqh01.mqcollect mqcollect
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager PCMS1.
1 : display qlocal(*) curdepth
AMQ8409: Display Queue details.
QUEUE(AMQ.MQEXPLORER.66061296) TYPE(QLOCAL)
CURDEPTH(0) AMQ8409: Display Queue details.
QUEUE(CUSTOMER.CMSADDRESS.UPDATE.LQ) TYPE(QLOCAL)
CURDEPTH(0) AMQ8409: Display Queue details.
QUEUE(CUSTOMER.CMSLEDGER.TRANSACTION.CREATE.LQ)
TYPE(QLOCAL) CURDEPTH(0)
…
…
…
AMQ8409: Display Queue details.
QUEUE(SYSTEM.PENDING.DATA.QUEUE) TYPE(QLOCAL)
CURDEPTH(0) One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
I’ve highlighted the first line as I think that this may be important.
At the xymon server I have added the following stanza to the analysis.cfg file: -
HOST=ukclaqh01
# MQ_QUEUE CUSTOMER.*
MQ_QUEUE "CUSTOMER.CMSADDRESS.UPDATE.LQ"
MQ_QUEUE SYSTEM.CLUSTER.REPOSITORY.QUEUE [depth-warning=1]
MQ_CHANNEL *
But… no joy! Any help would be gratefully received.
Ross
list Mike Russo
I noticed this old message from June 2011 (http://lists.xymon.com/archive/2011-June/031906.html) and unfortunately I'm running into the same problem with MQ monitoring. I get the "client data" from the collector, but the server doesn't seem to want to do anything with it. Is this the correct syntax? And do I have to put anything else in bb-hosts to get it to work? Here's the line from analysis.cfg for my host: HOST=testmq1.readq.local MQ_QUEUE Q1 depth-warning=10 depth-critical=20 MQ_QUEUE Q2 depth-warning=10 depth-critical=20 MQ_QUEUE Q3 depth-warning=10 depth-critical=20 -- Michael Russo, ReadQ Systems Inc. 1 Whitehall Street, 16th Floor, NY NY 10004
list Henrik Størner
▸
On 17-07-2013 20:59, Mike Russo wrote:
I noticed this old message from June 2011 (http://lists.xymon.com/archive/2011-June/031906.html) and unfortunately I'm running into the same problem with MQ monitoring. I get the "client data" from the collector, but the server doesn't seem to want to do anything with it.
The MQ handler is not enabled by default in the xymond_client module. Change tasks.cfg to start xymond_client with "--collectors=default,mqcollect" I don't think this is really documented anywhere - will have to fix that.
▸
Here's the line from analysis.cfg for my host:
HOST=testmq1.readq.local
MQ_QUEUE Q1 depth-warning=10 depth-critical=20
MQ_QUEUE Q2 depth-warning=10 depth-critical=20
MQ_QUEUE Q3 depth-warning=10 depth-critical=20Looks OK Regards, Henrik
list Mike Russo
▸
The MQ handler is not enabled by default in the xymond_client module. Change tasks.cfg to start xymond_client with "--collectors=default,mqcollect"
OK, I have modified tasks.cfg for the regular client channel. Now the process command line looks like: bb 16733 16729 0 17:16 ? 00:00:00 xymond_channel --channel=client --collectors=default,mqcollect --log=/var/log/xymon/clientdata.log xymond_client Not yet seeing any change in the main BB page however (I may have to wait a bit for it to regenerate) but is this correct?