WebSphere MQ Queue Details Test

This test connects to a WebSphere MQ server, auto-discovers the local queues that have been configured for this server, and provides detailed reports on the messages being added to and removed from each of the local queues.

Target of the test : A WebSphere MQ server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every local queue configured for the WebSphere MQ server

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed .


The host for which the test is to be configured.


The port number at which the specified host listens.


If you want to login as a specific MQ user to execute this test, then specify a valid user name in the User text box. The test will fail if an invalid user name is specified here. If no such authentication is required, then this parameter can be set to 'none'.


If a specific User is entered, then the password of that user has to be specified in the Password text box.

Confirm Password

Confirm the password by retyping it in the Confirm Password text box.


The name of the server connection channel for the WebSphere MQ server. The default value is "SYSTEM.DEF.SVRCONN". If you prefer not to use this default server connection channel for monitoring purposes, then you can create a custom channel in the WebSphere MQ server and use it for monitoring. The steps for achieving this have been detailed in Creating a Custom Channel topic.


If SYSTEM queues are to be monitored, then set the IgnoreSystemQueues flag to No. If not, set the flag to Yes.


Specify a comma-separated list of queue names or queue name patterns to be monitored. For example, your specification can be: VIDEO_*,*.NDURABLE.*,*_TDS_IN. In this case, the test will monitor only those queues with names that begin with “VIDEO_”, names that contain the string “.NDURABLE.”, and names that end with “_TDS_IN”.


If a SYSTEM queue or a pattern that matches a SYSTEM queue is configured in the IncludeQueues text box, then this test will monitor such SYSTEM queues, even if the IgnoreSystemQueues flag is set to Yes.


Denotes the time limit beyond which the eG agent regards a message as a delayed message. For e.g., if the DelayLimit is 300, the eG agent will regard all messages that have remained in the queue for 5 mins or more as a delayed message.


Takes a default value of "none". If so, none of the queues (other than the SYSTEM queues) are ignored while monitoring an MQ server. Otherwise, this parameter represents a comma separated list of queue names or queue name patterns. Any queue name that matches one of the patterns specified for this test is not considered for monitoring by the eG agent. For example, your specification can be:*.MQSC.*,*_XML_IN. In this case, the test will not monitor those queues with names that begin with that contain the string “.MQSC.”, and names that end with “_XML_IN”.


Specify the number of messages to be displayed in the detailed diagnosis of the test against this parameter.


When the number of messages lying in the queues exceed a limit specified here, an alert will be generated to notify administrator of large number of messages be kept in the queues.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

New messages added

The number of new messages added to the queue.


To compute this measure, the agent remembers the messages in the queue at the end of a measurement period, and then compares the messages that are in the queue during the next measurement period.

Old messages removed

The number of old messages removed from the queue during the last measurement period.


To track this metric, the agent tracks the messages in the queue at any instant of time. If a message is not available when the agent checks the queue again, the message is added to the count of old messages removed.

Delayed messages

The number of messages currently in the queue that have been lying in the queue for more than the DelayLimit.


The time when the message was put into the queue is used to determine how long the message has been delayed. If this test is being executed from a remote agent (i.e., not the local agent), it is essential that the system time of the remote agent and the system that hosts the MQ server are synchronized.

Detailed diagnosis for this measure provides details about which messages have been delayed. Information such as the PutDate (when the message was added to a queue), the message ID, the application that put the message, the sequence number of the message, the OS user who is running the application, and the length of the message is reported as part of the detailed diagnosis for this test.

Avg time in queue

The average time that a message has remained in the queue.


This metric is computed by determining how many messages are in the queue, and determining the time that each message has been in the queue.

Max time in queue

The maximum time that any of the current messages has spent in the queue.


This value can give an indication if any message is not being removed from the queue for an unusually long period.