java - IBM Websphere MQ Monitoring -

I'm trying to monitor with Hayprik headquarters of some performance figures spring source of IBM WebSphere MQ.

I am being provided for messages to be ensured and queue messages consumed by our local application and after the queue rate of some local queues, after the rate of repetition.

Initially, attempts to obtain data using WMI and window display counters seem to be that counter is not available for any local queue (only temporary queue load) on one of our servers And the counter is available on the other but do not always make a return value correctly though WMI.

I have used PCF (using MQIA_MSG_DEQ_COUNT ) which will not provide the requested counter. Mkyusisi ( DIVE QUEUE & amp; using DISPLAY QSTATUS ) that does not support Kyuiing rates - only the last message received / date and time.

Has anyone ever realized how WMI and performance counters are able to work correctly or get alternatives to WMI, which can provide me with the necessary data?

MQIA_MSG_DEQ_COUNT , you should know about RESET_QUEUE_STATISTICS < / code> command this gives what I "of quantum says physics properties that Dbluemkyu" it is precisely because the value of the function value of observation is restored If you are only questioned on the same value You have only one thread for investigation but if you have a lot of inquiries at one go, then they Each counter at each counter resets the counter, every step of each other, this aspect provides limited access to real time debugging RESET_QUEUE_STATISTICS and suitable for collecting reliable data is not.

Alternatively, use the MQ Accounting and Statistics feature. For QMgr to prepare accounting and data messages, it is necessary to enable them on QMGR or per-queue basis. Instructions for enabling them are in the manual section .

Note that the statistics are reported in an incident queue and they should be parsed and paused. To parse event messages, the document is in the reference section, in the named format, there is a sample program that describes how to format and format the data. The compiled version is also supplied to provide a human-readable list of such messages.

Once you have enabled the data on the row of interest and there is a way to parse the messages, then just point your parser and gather the figures in the appropriate event queue. Figures are not available, an example of the production of amqsmon is as follows:

  RECORDTYPE: QueueStatistics QueueManager: 'saturn.queue.manager' IntervalStartDate: '2005/04/30' IntervalStartTime: '15 09.02 'IntervalEndDate:' 2005/04/30 'IntervalEndTime: '15 .39.02' CommandLevel: 600 ObjectCount: 3 QueueStatistics: QueueName: 'LOCALQ' CreateDate: '2005/03/08' CreateTime: '17 .07.02 'QueueType: predefined QueueDefinitionType: local QMinDepth: 0 QMaxDepth: 18 AverageQueueTime: [29,827,281, 0] PutCount: [26, 0] PutFailCount: 0 Put1Count: [0, 0] Put1FailCount: 0 PutBytes: [88, 0] GetCount: [18, 0] GetBytes: [52, 0] GetCalCount: 0 BrowseCount: [0, 0] BrowseBytes: [0, 0] BrowseFailCount: 1 NonQueuedMsgCount: 0 ExpiredMsgCount: 0 PurgedMsgCount: 0   
 This and other Example    < / P>