CA Nimsoft Monitordocs.nimsoft.com/.../1.0/websphere_mq-1.0.pdf · websphere_mq Node ... This guide helps the CA Nimsoft Monitor Administrator understand the configuration of

Probe Guide for WebSphere MQ Monitoring websphere_mq v1.0 series

CA Nimsoft Monitor

CA Nimsoft Monitor Copyright Notice

This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (th

Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy.

The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed.

WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The manufacturer of this System is CA.

Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Legal information on third-party and public domain software used in the Nimsoft Monitor solution is documented in Nimsoft Monitor Third-Party Licenses and Terms of Use (http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html).

http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html

Contact CA

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

Online and telephone contact information for technical assistance and customer services

Information about user communities and forums

Product and documentation downloads

CA Support policies and guidelines

Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

Send comments or questions about CA Technologies Nimsoft product documentation to [email protected].

To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

http://www.ca.com/support

mailto:[email protected]

http://www.ca.com/docs

Contents 5

Contents

Chapter 1: Overview 7

About This Guide .......................................................................................................................................................... 7

Related Documentation ............................................................................................................................................... 8

Preconfiguration Requirements ................................................................................................................................... 8

Supported Platforms ............................................................................................................................................. 8

Enable the Queue Monitors .................................................................................................................................. 9

Root User Authorization for MQI Calls .................................................................................................................. 9

Chapter 2: Configuration Details 11

websphere_mq Node ................................................................................................................................................. 11

Queue Manager Node ......................................................................................................................................... 13

Start Monitoring ......................................................................................................................................................... 15

How to Configure Alarm Thresholds in websphere_mq ............................................................................................ 16

Activate QoS Data for Monitors ................................................................................................................................. 17

Stop Receiving Alarms for Deleted Components ....................................................................................................... 17

Manage System Channels Monitoring ....................................................................................................................... 18

Chapter 3: websphere_mq QoS Metrics 21

Chapter 4: Known Issues 25

6 Probe Guide for WebSphere MQ Monitoring

Documentation Changes

This table describes the version history for this document.

Version Date What's New?

1.0 June 2014 Initial Release


Chapter 1: Overview

IBM WebSphere MQ is messaging middleware that allows you to share data and messages asynchronously between applications across multiple platforms. WebSphere MQ allows independent and potentially non-concurrent applications on a distributed system to communicate with each other. Applications can put or get data through WebSphere MQ messaging queues.

IBM WebSphere MQ defines logical containers that are named Queue Managers (QMs) for managing the storage and recovery of data. QMs coordinate with the applications that are updating messages on the queues, and perform queue isolation and locking functions to maintain consistency. WebSphere MQ messaging queues are used either to store messages from programs or are pointers to other queues. Channels are defined as a logical communication link between QMs. WebSphere MQ supports the message exchange in both point-to-point and publish/subscribe mode.

The WebSphere MQ Monitoring (websphere_mq) probe is installed locally on a system with IBM WebSphere MQ. The probe discovers the available QMs and the corresponding messaging queues, channels, topics, and subscriptions. You can monitor and generate alarms for:

Queue Managers

Messaging Queues

Channels

This section contains the following topics:

About This Guide (see page 7) Related Documentation (see page 8) Preconfiguration Requirements (see page 8)

About This Guide

This guide helps the CA Nimsoft Monitor Administrator understand the configuration of the WebSphere MQ Monitoring probe and provides the following information:

Overview of the WebSphere MQ Monitoring probe and other related documentation.

Configuration details of the probe.

Field information and common procedures for configuring the probe.

Important! Description for the intuitive GUI fields is not included in the document.

Related Documentation


Related Documentation Related Documentation

Documentation for other versions of the websphere_mq probe

The Release Notes for the websphere_mq probe

User documentation for the Admin Console

Monitor Metrics Reference Information for CA Nimsoft Probes (http://docs.nimsoft.com/prodhelp/en_US/Probes/ProbeReference/index.htm)

Preconfiguration Requirements

The preconfiguration requirements of the WebSphere MQ Monitoring probe are as follows:

Install the probe on the system where IBM WebSphere MQ is running.

Note: The probe supports only 7.5.0.X and 7.0.1.X versions of IBM WebSphere MQ.

Install the appropriate MQSeries Java version on the host system. For example, the MQSeriesJava-U200442-7.5.0-3.x86_64.rpm is required for monitoring 7.5.0.3 version of WebSphere MQ and the MQSeriesJava-7.0.1-3.x86_64.rpm is required for monitoring 7.0.1.3 version of WebSphere MQ. In case of multiple installations of WebSphere MQ, install the highest version of MQSeries Java.

Add hostname of the system, where the probe and IBM WebSphere MQ is installed, in the /etc/hosts file. You can use the vi /etc/hosts command for this purpose.

Ensure that command Server of the Queue Manager is up and running.

Supported Platforms

The WebSphere MQ Monitoring probe supports RHEL version 5.6 and 6.1.

Refer to the Compatibility Support Matrix for the latest information about supported platforms. See also the Support Matrix for Probes for more information about the websphere_mq probe.

http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/websphere_mq/ReleaseNotes/index.htm

http://docs.nimsoft.com/prodhelp/en_US/AdminConsole/6.5/index.htm

http://docs.nimsoft.com/prodhelp/en_US/Probes/ProbeReference/index.htm

http://support.nimsoft.com/downloads/doc/NMSCompatibility_SupportMatrix_current.pdf

http://support.nimsoft.com/downloads/doc/Platform_Support_Availability_current.pdf



Enable the Queue Monitors

The default configuration of IBM WebSphere MQ does not expose all monitoring data of the Message Queues to an external application. Therefore, when the WebSphere MQ Monitoring (websphere_mq) probe runs a command to fetch monitoring data, WebSphere MQ does not return any value for the following monitors:

Oldest Message Age

On Queue Time

Time Since Last Put

Time Since Last Get

Set the MONQ property value of the message queue to LOW, MEDIUM, or HIGH for fetching the monitoring data. The recommended value is HIGH.

Follow these steps:

1. Open the Linux terminal.

2. Go to the installation directory of WebSphere MQ. The default location is /opt/mqm/bin.

3. Go to the Queue Manager of the target message queue, you want to monitor. For example, if your Queue Manager name is QM1, you can execute the following command:

./runmqsc QM1

4. Execute the DISPLAY ALL command and verify if the MONQ property value is OFF.

5. Execute the ALTER QMGR MONQ(HIGH) command and change the MONQ property value to HIGH for all message queues.

Alternatively, execute the ALTER QLOCAL(MYQUEUE.Q) MONQ(HIGH) for changing the MONQ property value to HIGH for the given message queue. The QLOCAL is the queue type and MYQUEUE is the queue name.

The MONQ property value is changed to HIGH, therefore, allowing the probe to collect monitoring data about the message queues in the subsequent interval.

Root User Authorization for MQI Calls

The Message Queue Interface (MQI) calls are used for accessing QMs and its related components of WebSphere MQ installation. Any user of the mqm user group has rights for executing these MQI calls. However, the WebSphere MQ Monitoring probe has the root user rights in the Linux environments. This root user is not added to the mqm user group, by default. Therefore, the probe requires the root user to be added in the mqm user group, for monitoring WebSphere MQ.



However, adding root user to the mqm group can cause security threats to the target system and WebSphere MQ. Therefore, the recommendation is to use the setmqauth command for authorizing the root user to execute the MQI calls for each QM.

The WebSphere MQ Monitoring probe is shipped with a script file, setmqprobe_auth.sh, which uses the setmqauth command for authorizing the root user to execute the MQI calls. This option does not require you to add the root user to the mqm user group.

Follow these steps:

1. Open the Linux terminal.

2. Go to the probe installation directory. The default location is /opt/Nimsoft/probes/application/websphere_mq.

3. Set the execution rights for the script by executing the chmod +x setmqprobe_auth.sh command.

4. Log in as mqm user by executing the su -mqm command.

5. Execute the setmqprobe_auth.sh script using the following command:

./setmqprobe_auth.sh [QM Name] [All]

QM Name: identifies the actual QM name, for which you want to authorize the root user for executing the MI calls.

All: discovers all QMs of WebSphere MQ installation and authorize the root user for executing the MQI calls on all QMs.

Note: You can use only one of the given parameters and without brackets. Recommendation is to use the All parameter when probe is deployed for the first time and later the QM Name.

The script prompts you to give the WebSphere MQ installation path where the bin folder exists.

6. Define the path and press Enter.

The script uses the default path /opt/mqm.

The probe reads WebSphere MQ configuration and updates the root user access for given QMs. The probe is now ready to fetch the monitoring data of WebSphere MQ.

Important! In case, a QM is not activated the script throws the AMQ7028: The queue manager is not available for use error. You can restart the QM and then execute the script again. Similarly, run the script again for newly discovered QMs also.


Chapter 2: Configuration Details

The WebSphere MQ Monitoring probe is configured for setting up the monitoring parameters of the QMs, channels, and queues. The probe automatically discovers the available QMs and other components of WebSphere MQ.

Note: Ensure that preconfiguration requirements are fulfilled before configuring the probe.

This section explains each node of the probe GUI with their corresponding field descriptions and standard procedures of the probe.

This section contains the following topics:

websphere_mq Node (see page 11) Start Monitoring (see page 15) How to Configure Alarm Thresholds in websphere_mq (see page 16) Activate QoS Data for Monitors (see page 17) Stop Receiving Alarms for Deleted Components (see page 17) Manage System Channels Monitoring (see page 18)

websphere_mq Node

The websphere_mq node lets you view the probe information and configure auto discovery properties of the probe.

Navigation: websphere_mq

Set or modify the following values as required:

websphere_mq > Probe Information

This section provides information about the probe name, probe version, probe start time, and the probe vendor.

websphere_mq > General Configuration

This section is used to configure log level of the probe.

Log Level: specifies the detail level of the log file.

Default: 3- Info

websphere_mq Node


websphere_mq > WMQ Auto Configuration

This section is used to configure the automatic discovery and configuration properties of the probe. These properties are applied to all the QMs, which the probe discovers.

Auto Discovery Interval (min): defines the time interval for fetching the updated configuration of WebSphere MQ. For example, if you have defined a new Queue Manager (QM), it reflects on the probe GUI after this interval.

Default: 60

Default Interval (secs): specifies the default time interval after which the probe queries WebSphere MQ for fetching the monitoring data. The probe also updates the QM definitions after this interval. For example, probe displays the updated queue details on the probe interface.

Default: 300

Activate All QM: activates all the QMs for monitoring as soon as the probe discovers them. This option does not activate QoS for the QMs. Activating the QMs displays the corresponding queues on the probe GUI.

Note: This functionality works only for the QMs, which are discovered after first deployment of the probe.

Channel Status Coding Scheme: specifies the channel status coding scheme for displaying the channel status as provided by IBM or as configured in the probe. The following table describes both coding schemes:

Channel Status IBM MQ Native Coding Scheme Nimsoft Coding Scheme

Stopped 6 0

Paused 8 1

Inactive -1 2

Stopping 4 3

Initializing 13 4

Starting 2 5

Switching Channel 14 6

Retrying 5 7

Requesting 7 8

Binding 1 9

Running 3 10

websphere_mq Node


The Nimsoft Coding Scheme is defined in increasing order of channel health status for configuring thresholds on the Channel Status metric.

Note: The probe returns the most positive channel status when multiple instances of the same channel exist. The highest Nimsoft Coding scheme code defines the most positive status.

websphere_mq > WMQ Configuration

This section lets you configure WebSphere MQ properties for allowing the probe to connect and query WebSphere MQ.

WMQ Installation Path: defines the WebSphere MQ installation path where the bin folder exists. In case, you have multiple installations of the WMQ on the same system, give path for the highest version.

Notes:

Do not include bin in the path. For example, if your WMQ installation is at /opt/mqm/bin, then your path would be /opt/mqm. Use the Verify Path option of the Actions drop-down list for validating the path.

Use the Discover QM Changes option of the Actions drop-down list and update QM changes on the probe GUI manually before the Auto Discovery Interval.

Queue Manager Node

The Queue Manager node is a container for all queue manager name node, which are detected by the probe for monitoring.

<Queue Manager Name> Node

The queue manager name node represents the actual QM name and lets you activate the QM monitors.

Navigation: websphere_mq > Queue Manager > queue manager name


queue manager name > Resource Setup

This section lets you configure properties of the QM for getting the monitoring data.

Interval (secs): specifies the time interval after which the probe queries the QM for fetching the monitoring data. The probe also updates the QM definitions, for example updated queue information, after this interval.

Activate: activates monitoring of the QM. The probe loads QM definitions on the probe GUI after selecting and saving this option.

websphere_mq Node


Alarm Message: specifies the alarm message when the QM is down or not reachable. Select one of the following options:

ResourceCritical: generates the alarm message with the Critical alarm severity.

ResourceError: generates the alarm message with the Error alarm severity.

Default: ResourceCritical

Instance Name: identifies the WebSphere MQ installation name in which the QM is available, because a single system can have multiple instances of WebSphere MQ. If WebSphere MQ version is 7.0x, this field remains blank.

queue manager name > Monitors

This section lets you select a particular counter from a list and activate the QoS and alarms. Refer Configure the Monitoring Counters section for the detailed process.

Note: The Queue Manager Uptime monitor value is always NULL when monitoring WebSphere MQ 7.0.1.10.

Channel Node

The Channel node is a container for various channel type nodes. The probe supports monitoring for the following types of channel:

Server

Sender

Receiver

Requester

Server Connection

Cluster Sender

Cluster Receiver

Select any of the available channel type node for monitoring.

<Channel Type> Node

The channel type node contains a channel name node for each channel that is detected by the probe.

<Channel Name> Node

Start Monitoring


The channel name node represents the actual channel name and becomes visible when the QM monitoring is activated for monitoring in the Queue Manager node.

Navigation: websphere_mq > Queue Manager > queue manager name > Channel > channel type > channel name


channel name > Monitors

This section lets you select channel monitors from a list and activate the QoS data and alarms. Refer Configure the Monitoring Counters section for the detailed process.

Queue Node

The Queue node ia container for all queue name nodes, which are configured on the QM for monitoring.

Note: The probe monitors only local queues.

<Queue Name> Node

The queue name node represents the actual message queue name and becomes visible when the QM monitoring is activated for monitoring.

Navigation: websphere_mq > Queue Manager > queue manager name > Queue > queue name


queue name > Monitors

This section lets you select a particular counter from a list and activate the QoS and alarms. Refer Configure the Monitoring Counters section for the detailed process.

Start Monitoring

After deploying the probe for the first-time it displays only the websphere_mq node in the navigation pane. The probe requires initial configuration for discovering WebSphere MQ installation and to start monitoring.

Follow these steps:

1. Click the websphere_mq node.

2. Configure the following fields of the WMQ Auto Configuration section:

Auto Discovery Interval (min)

How to Configure Alarm Thresholds in websphere_mq


Default Interval (secs)

Activate All QMs

Channel Status Coding Scheme

3. Configure the WMQ Installation Path field of the WMQ Configuration section for connecting and querying WebSphere MQ.

Note: Refer the websphere_mq Node topic for the field description.

4. Select the Verify Path option from the Actions drop-down list of the WMQ Configuration section.

The probe displays a success message after connecting to WebSphere MQ else an error message is displayed.

5. Click Save.

The probe saves the updated configuration, queries WebSphere MQ, and loads WebSphere MQ details on the probe GUI. Eventually, the process takes some time and displays the PPM-023 error that probe configuration cannot be loaded.

6. Click Retry on the error dialog until WebSphere MQ details are displayed on the probe GUI.

The list of all QMs is displayed in the navigation pane of the probe GUI. The other related components of the QM take up to one measurement interval for displaying them on the probe interface.

How to Configure Alarm Thresholds in websphere_mq

Some Quality of Service measurement probes allow you to set different types of alarm thresholds. These threshold options allow you to more broadly control when alarm messages are sent for each QoS probe.

For more information about the different alarm thresholds and their configuration requirements, refer to the General Probe Configuration section of the Admin Console Help.

Important! Alarm threshold settings are dependent on the baseline_engine probe. If you do not have the correct version of baseline_engine configured, you will not see the additional threshold options.

Activate QoS Data for Monitors


Activate QoS Data for Monitors

After loading WebSphere MQ details on the probe GUI you can activate QoS data for various monitors of QM, channels, and message queues. The QoS data helps you understand the trend for the specific monitor. The process of activating QoS is identical for QM, channels, and message queues.

Follow these steps:

1. Navigate to the appropriate queue manager name node in the navigation pane.

The list of available monitors is displayed on the probe GUI.

2. Select the appropriate monitor from the Monitors section of the probe GUI for which you want to activate the QoS data.

3. Select the Publish Data check box for generating QoS data for the monitor.

Refer the How to Configure Thresholds in websphere_mq topic for configuring dynamic and static thresholds for generating alarms.

4. Click Save.

The probe saves the updated configuration and generates QoS for the configured monitor.

Note: Avoid saving the configuration frequently because the probe takes considerable time after saving and reloading the configuration. The recommendation is to configure all necessary monitors at once and then save configuration.

Stop Receiving Alarms for Deleted Components

Use this procedure to stop getting alerts for any WebSphere MQ component you delete. For example, you are monitoring a local queue, which is deleted from the queue manager before deactivating its monitoring. The probe is not able to query the queue details and generates the false alerts because the queue is deleted from WebSphere MQ configuration.

Modify the detach configuration parameter of the probe to stop receiving false alerts.

Follow these steps:

1. Open the Raw Configuration GUI of the probe.

2. Add the show_detached_configuration key under the setup section and set the key value to yes.

Manage System Channels Monitoring


3. Restart the probe for applying the changes.

The navigation pane of the probe GUI shows a new node Detached Configuration. This node contains the components which are deleted from WebSphere MQ but still selected for monitoring in the probe.

4. Click the Options icon next to the component name you want to stop receiving alerts and select Delete.

5. Click Save.

Now the probe stops sending false alerts for the deleted components.


IBM WebSphere MQ consists of ten system channels, which define the WebSphere MQ channel schema for transferring messages between applications. The default configuration of the probe lets you monitor only three system channels out of 10, which are as follows:

SYSTEM.AUTO.RECEIVER*

SYSTEM.AUTO.SVRCONN*

SYSTEM.DEF.CLUSRCVR

SYSTEM.DEF.CLUSSDR

SYSTEM.DEF.RECEIVER



SYSTEM.DEF.REQUESTER

SYSTEM.DEF.SENDER

SYSTEM.DEF.SERVER

SYSTEM.DEF.SVRCONN*

SYSTEM.DEF.CLNTCONN

Note: The channel names, which are marked with an asterisk (*) are available for monitoring, by default. The other channels are unmonitored, by default, as they do not provide any valid monitoring data.

You can manage (add or remove) your system channels list and fulfill your system channel monitoring requirement.

Follow these steps:

1. Open the Raw Configure GUI of the probe.

2. Go to the disabledSystemChannelList key under the setup section.

3. Edit the key value by providing the system channel names in a comma-separated format. For example, use Channel1,Channel2 for excluding Channel1 and Channel2 monitoring.

4. Click Apply.

5. Close the Raw Configuration GUI.

6. Restart the probe for applying the changes.

The system channels, which are configured in the disabledSystemChannelList key are excluded from the probe GUI.


Chapter 3: websphere_mq QoS Metrics

This section contains the QoS metrics for the websphere_mq probe.

QoS Name Metric Name

Unit Description

Queue Manager (Resource)

QOS_QUEUE_MANAGER_CONNECTION_COUNT

Connection Count

Count Current number of connections to the queue manager.

QOS_QUEUE_MANAGER_CHANNEL_INITIATOR_STATUS

Channel Initiator Status

Status Status of the channel initiator.

QOS_QUEUE_MANAGER_COMMAND_SERVER_STATUS

Command Server Status

Status Status of the command server.

QOS_QUEUE_MANAGER_UP_TIME

Up Time Hours Queue manager up time. This value is always NULL for WebSphere MQ 7.0.1.10.

Channel

QOS_CHANNEL_BATCH_COUNT

Batch Count

Count Number of batches completed.

QOS_CHANNEL_BUFFERS_RECEIVED

Buffers Received

Count Number of buffers received.

QOS_CHANNEL_BUFFERS_SENT

Buffers Sent

Count Number of buffers sent.

QOS_CHANNEL_BYTES_RECEIVED

Bytes Received

Bytes Number of bytes received.

QOS_CHANNEL_BYTES_SENT Bytes Sent Bytes Number of bytes sent.

QOS_CHANNEL_COMPRESSION_RATE

Compression Rate

Percent Compression rate achieved to the nearest percentage.

QOS_CHANNEL_COMPRESSION_TIME

Compression Time

Microseconds

Time spent per message during compression or decompression.

QOS_CHANNEL_EXIT_TIME_PER_MESSAGE

Exit Time Per Message

Microseconds

Indicator of the time taken for executing user exits per message.




Unit Description

*QOS_CHANNEL_LONG_RETRIES_LEFT

Long Retires Left

Count Number of long retries remaining.

*QOS_CHANNEL_MCA_STATUS

MCA Status

Status Status of Message Channel Agent (MCA).

QOS_CHANNEL_MESSAGE_COUNT

Message Count

Count Number of messages sent or received.

*QOS_CHANNEL_SHORT_RETRIES_LEFT

Short Retries Left

Count Number of short retries remaining.

*QOS_CHANNEL_CHANNEL_SUB_STATE

Channel Sub State

Status Current action being performed by the channel.

*QOS_CHANNEL_TRANSMISSION_QUEUE_TIME_INDICATOR

Transmission Queue Time Indicator

Microseconds

Time for which messages remained on the transmission queue before retrieving.

QOS_CHANNEL_TIME_SINCE_LAST_MESSAGE

Time Since Last Message

Hours Time since last message sent or MQI call handled.

QOS_CHANNEL_UP_TIME Up Time Minutes Channel up time.

QOS_CHANNEL_CHANNEL_STATUS

Channel Status

Status Status of the channel.

#QOS_CHANNEL_AVERAGE_COMPRESSION_RATE

Average Compression Rate

Percent Average compression rate achieved to the nearest percentage.

#QOS_CHANNEL_AVERAGE_COMPRESSION_TIME

Average Compression Time

Microseconds

Average time spent per message during compression or decompression.

#QOS_CHANNEL_AVERAGE_EXIT_TIME_PER_MESSAGE

Average Exit Time Per Message

Microseconds

Indicator of the average time taken for executing user exits per message.

Queue

QOS_QUEUE_CURRENT_DEPTH

Current Depth

Count Number of messages in the queue.




Unit Description

QOS_QUEUE_OPEN_INPUT_COUNT

Open Input Count

Count Number of applications that are currently connected to the queue to put messages on the queue.

QOS_QUEUE_OPEN_OUTPUT_COUNT

Open Output Count

Count Number of applications that are currently connected to the queue to get messages on the queue.

QOS_QUEUE_UNCOMMITTED_MESSAGE_COUNT

Uncommitted Message Count

Count Number of uncommitted changes (puts and gets) pending for the queue.

QOS_QUEUE_ON_QUEUE_TIME

On Queue Time

Microseconds

Time duration for which a message is in the queue.

QOS_QUEUE_OLDEST_MESSAGE_AGE

Oldest Message Age

Seconds Age of the oldest message in the queue.

QOS_QUEUE_UTILIZATION Utilization Percent Capacity utilization of the queue which is calculated as (Current Depth/Maximum Depth ) * 100.

QOS_QUEUE_TIME_SINCE_LAST_GET

Time Since Last Get

Seconds Time since the last message is successfully get to the queue.

QOS_QUEUE_TIME_SINCE_LAST_PUT

Time Since Last Put

Seconds Time since the last message is successfully put to the queue.

Note:

The QoS names marked with an asterisk (*) are not applicable for Requester, Receiver, Server Connection, and Cluster Receiver channels.

The QoS names marked with a hash (#) are only applicable for Requester, Receiver, Server Connection, and Cluster Receiver channels.

Chapter 4: Known Issues 25

Chapter 4: Known Issues

The Channel Status metric of a sender channel is displayed as Batch Count on the Unified Service Management (USM) portlet of the Unified Management Portal (UMP).

Documents

CA Nimsoft Monitordocs.nimsoft.com/.../1.0/websphere_mq-1.0.pdf · websphere_mq Node ... This guide helps the CA Nimsoft Monitor Administrator understand the configuration of