Skip to main content

IBM WebSphere MQ Metrics - Middleware News

IBM WebSphere MQ Metrics
=========================

WebSphere MQ (formerly MQSeries) is IBM's Message Oriented Middleware offering that allows independent and potentially non-concurrent applications on a distributed system to communicate with each other.

This chapter provides descriptions for all IBM WebSphere MQ metric categories, and tables list and describe associated metrics for each category.

Channel Current Status Metrics
==============================

This category provides metrics about the current status of the channel.

Default Collection Interval — Every 3 minutes


Table 3-1 Channel Current Status Metrics
-------------------------------------------

Metric Description

Bytes Received


Shows the number of bytes received.

Bytes Sent


Shows the number of bytes sent

Delta Bytes Received


Shows the number of bytes received since last collection

Delta Bytes Sent


Shows the number of bytes sent since last collection

Delta Messages Sent/Received


Shows the number of messages processed since last collection

Messages Sent/Received


Shows the number of messages processed

Status


Shows the current status.


Channel Saved Status Metrics
=============================

This category provides metrics about Channel Saved Status.

Default Collection Interval — Every 2 minutes



Table 3-2 Channel Saved Status Metrics
---------------------------------------

Metric Description

Last Seq Number


Shows the sequence number of the last message sent

Status


Shows the status of the channel

Type


Shows the type of the channel

Xmit Queue


Shows the transmission queue used by sender channels

Channels Metrics

This category provides metrics related to the channels.

Default Collection Interval — Every 10 minutes


Table 3-3 Channels Metrics
-----------------------------

Metric Description

Alteration Date


Shows the date on which the definition was last altered

Cluster Name


Shows the name of the IBM WebSphere MQ Cluster to which this channel belongs

Cluster Name list


Shows the cluster name list

Connection Name


Shows the name of the channel connection

Max Msg Length


Shows the maximum length of the message that can be processed by the channel

Type


Shows the type of the channel

Xmit QName


Shows the name of the transmission queue used by the sender channels

DynamicQs Metrics

This category provides metrics related to Dynamic Queues.


Table 3-4 DynamicQs Metrics
----------------------------

Metric Description

Definition Type


Shows the type of queue definition

Type


Shows the type of the queue

Usage


Shows information about the usage (normal/transmission)

Local Queues Metrics

This category shows metrics related to local queues.

Default Collection Interval — Every 10 minutes


Table 3-5 Local Queues Metrics
------------------------------

Metric Description

Cluster Name List


Shows the cluster Name List

Definition Type


Shows the type of the queue definition

Depth


Shows the number of messages on the queue

Max Depth


Shows the maximum number of messages on the queue

Max Message Length


Shows the maximum length of the message can be processed

Open Input Count


Shows the number of open input handles, that is the total handles open for input on this queue. This gives you an idean on the number of applications that are currently connected to the queue to put messages on the queue

Open Output Count


Shows the number of open output handles, that is the total handles open for output on this Queue. This gives you an idea on the number of applications that are currently connected to the queue to get messages from the queue

Percent Usage


Shows the space used (in percentage)

Type


Shows the type of the queue

Usage


Shows details about the usage, which can be "Normal" or "Trasmission")

Xmit QName


Shows the name of the transmission queue



QM Cluster Metrics
======================

This category provides metrics related to IBM Websphere MQ Queue Manager Cluster, mainly the details about the channel used, the queue manager within this cluster, and the type of queue manager that is within this cluster.

Default Collection Interval — Every 10 minutes



Table 3-6 QM Cluster Metrics
-----------------------------

Metric Description

Queue Manager Name


Shows the name of the IBM Websphere MQ Queue Manager that is within this IBM Websphere MQ Queue Manager Cluster

Queue Manager Type


Shows the type of the IBM Websphere MQ Queue Manager (full/partial repository)

QM General Metrics

This caterogy provides metrics related to QM General.

Default Collection Interval — Every 2 minutes



Table 3-7 QM General Metrics
----------------------------

Metric Description

Command QName


Shows the name of the local queue that is used for accepting commands

Dead Letter QName


Shows the name of the local queue that is to be used for undelivered messages

Default Xmit QName


Shows the name of the default transmission queue that is used for the transmitting messages to remote queue managers, if there is no other indication of which transmission queue to use

Max Handles


Shows the maximum number of handles that any one job can have open at a time

Max Message Length


Shows the maximum length of message that can be processed

Platform


Shows the platform on which the queue manager is running

Repository Name List


Shows a list of clusters for which this queue manager provides a repository service

QMLoad Metrics

This category provides metrics about the load on IBM Websphere MQ Queue Manager.



Table 3-8 QMLoad Metrics
-----------------------

Metric Description

Bytes Received


Shows the bytes received since last collection

Bytes Sent


Shows the bytes sent since last collection

Messages Sent/Received


Shows the messages sent or received since last collection



Queue Status Input Handle Metrics
===================================

This category provides metrics related to Queue Status Input Handle.

Default Collection Interval — Every 10 minutes



Table 3-9 Queue Status Input Handle Metrics
-------------------------------------------

Metric Description

Appl Tag


Shows the name of the application that is using this queue

Appl Type


Shows the type of the application that is using this queue

Channel Name


Shows you the channel used for the message input

Connection Name


Shows the name of the connection used by the channel

Open Options


Shows the open options for the queue

User Identifier


Shows you the user ID of the application


Queue Status Output Handle Metrics
==================================

This category provides metrics related to Queue Status Output Handle.

Default Collection Interval — Every 10 minutes


Table 3-10 Queue Status Output Handle Metrics
------------------------------------------------

Metric Description

Appl Tag


Shows the name of the application that is using this queue

Appl Type


Shows the type of the application that is using this queue

Channel Name


Shows the name of the channel used for the message output

Connection Name


Shows the name of the connection name used by the channel

Open Options


Shows the open options for this queue

User Identifier


Shows the user ID of the application

Queues Metrics

This category provides metrics related to Message Queues.

Default Collection Interval — Every 10 minutes


Table 3-11 Queues Metrics
--------------------------

Metric Description

Cluster Name List


Shows the list of clusters with which the queue is shared

Depth


Shows the current depth (number of messages) of the queue. For this metric you can set different warning and critical threshold values for each "QName" object. If warning or critical threshold values are currently set for any "QName" object, those thresholds can be viewed on the Metric Detail page for this metric.

Max Depth


Shows the maximum depth (number of messages) of the queue

Max Message Length


Shows the maximum message length allowed on a queue

Open Input Count


Shows the number of open input handles, that is the total handles open for input on this Queue. This gives you an idea on the number of applications that are currently connected to the queue to put messages on the queue

Open Output Count


Shows the number of open output handles, that is the total handles open for output on this Queue. This gives you an idea on the number of applications that are currently connected to the queue to get messages from the queue

Remote QManager


Shows the name of the remote queue manager (only for remote queues)

Remote QName


Shows the remote queues with which this queue interacts

Type


Shows the queue type. It can be one of the following: Local, Remote, Model, Alias Queue, or Read-only

Use


Shows how the queue is being used. The usage types can be "Normal" or "Tramission"

Xmit QName


Shows the transmission queue associated with this queue (only for remote queues)

Response Metrics

This category provides status metrics.

Table 3-12 Response Metrics
-----------------------------
Metric Description

Response


Shows the current status of the Queue Manager. The evaluation and collection frequency is 1 minute. The upload frequency is after every 5 samples.

Sender Channel Qs Metrics

This category provides metrics related to the Sender Channel Queues.

Default Collection Interval — Every 10 minutes


Table 3-13 Sender Channel Qs Metrics
--------------------------------------

Metric Description

Xmit QName


Shows the name of the transmission queue

Comments

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201...

Message Broker (WMB) installation and setup on Linux

Message Broker (WMB) installation and setup on Linux Installing the Binaries As a first step download the trail version of the message broker binaries from IBM site and install them. this part is very simple and process is depends on your operating system. Like for windows, you have .exe file and Linux has rpm and unix you get pkg or other. After installation Set up a broker database [Windows] __ 1. Create the broker database, BRKDB. Open a WebSphere Message Broker Command Console: mqsicreatedb BRKDB This command also establishes the required ODBC connection. _ 2. Verify your user account for the broker database. [Linux] If you are creating Oracle databases for 32-bit brokers on Linux® and UNIX® systems, run the mqsi_setupdatabase command before you create a database. mqsi_setupdatabase– Database–Database_Home_Directory Eg:mqsi_setupdatabase oracle /oracle/product/9i/Db_1 Add $ORACLE_HOME/lib to the end of the MQSI_LIBPATH library search path environment variabl...