Chat now with support
Chat with Support

Foglight for IBM WebSphere MQ 5.5.5.9 - Installation Guide

Monitor lists properties

These secondary agent properties maintain a list of which queues and channels are to be monitored for a particular queue manager. Monitoring of each item in a list can be enabled or disabled.
 
* 
IMPORTANT: It is essential that each agent have its own queue and channel lists. Ensure that you clone a new list when you are first configuring your agent.
To set the monitor lists properties:
1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
2
On the Agent Status dashboard, select the instance of the MQ Agent whose properties you want to modify and click Edit Properties.
3
Locate the Monitor Lists properties.
4
Clone the defaultQueueList list.
a
From the Queue List, select defaultQueueList.
 
* 
IMPORTANT: This is a default, empty queue list. Selecting other, pre-populated queue lists (if available) and cloning them (as described in Step b) results in their list entries being copied to the destination list and requires their removal. For the same reason, you should not clone any queue lists populated by the auto-discovery process, unless the second list is expected to have the same queue names as the first list.
b
Click the Clone button to the right of Queue List to create a clone of the selected defaultQueueList.
In the dialog box that opens, type a name for the cloned list.
 
* 
IMPORTANT: Failing to clone the defaultQueueList causes it to be populated with entries that are carried over to the subsequent queue lists created by cloning this default list, and requires you to remove them manually from each cloned instance.
5
Update the newly cloned list.
You can add alias queues, and cluster queues on the monitored queue manager.
When auto-discovery is enabled, the MQ Agent needs some time to update the queue and channel lists. Changing the auto-discovery or editing these lists during the update is not recommended. Instead, you can make these changes either on deactivated MQ Agent instances, or on running agent instances that have a discovery collection frequency of five minutes or higher.
a
Click the Edit button to the right of Queue List.
b
In the dialog box that opens, click Add Row to add an entry.
For each row, define the following values:
 
* 
NOTE: If auto-discovery is enabled, the queue and channel lists are automatically populated.
Queue Name: Type the name of this queue.
Monitor: Select the check box to enable the monitoring of the queue, or clear the check box to disable monitoring.
c
Save your changes to the queue list by clicking Save Changes in the dialog box.
The dialog box closes.
6
Repeat Step 4 and Step 5 to create as many queue lists as necessary.
 
* 
NOTE: You must add a queue list for each MQ Agent instance.
7
Clone the defaultChannelList list.
a
From the Channel List, select defaultChannelList.
 
* 
IMPORTANT: This is a default, empty channel list. Selecting other, pre-populated channel lists (if available) and cloning them (as described in Step b) results in their list entries being copied to the destination list and requires their removal. For the same reason, you should not clone any channel lists populated by the auto-discovery process, unless the second list is expected to have the same channel names as the first list.
b
Click the Clone button to the right of Channel List to create a clone of the defaultChannelList.
In the dialog box that opens, type a name for the cloned list.
 
* 
IMPORTANT: Failing to clone the defaultChannelList causes it to be populated with entries that are carried over to the subsequent channel lists created by cloning this default list, and requires you to remove them manually from each cloned instance.
8
Update the newly-cloned list.
When auto-discovery is enabled, the MQ Agent needs some time to update the queue and channel lists. Changing the auto-discovery or editing these lists during the update is not recommended. Instead, you can make these changes either on deactivated MQ Agent instances, or on running agent instances that have a discovery collection frequency of five minutes or higher.
a
Click the Edit button to the right of Channel List.
b
In the dialog box that opens, click Add Row to add an entry.
For each row, define the following values:
 
* 
NOTE: If auto-discovery is enabled, the queue and channel lists are automatically populated.
Channel Name: Type the name of this channel.
Monitor: Select the check box to enable the monitoring of the channel, or clear the check box to disable monitoring.
c
Save your changes to the channel list by clicking Save Changes in the dialog box.
The dialog box closes.
9
Repeat Step 7 and Step 8 to create as many channel lists as necessary.
 
* 
NOTE: You must add a channel list for each MQ Agent instance.
10
Ensure that temporary objects are ignored during monitoring.
In the Exclude Objects Regex box, type a regular expression that selects temporary objects.
Use this property to specify a regular expression that selects temporary objects. The MQ Agent ignores any queue or channel objects whose names match the regular expression during auto-discovery.
In the regular expression “\.”, the backslash “\” is the escape character, and the period “.” matches any single character. Additionally, “.*” matches any strings, while the pipe character “|” is a separator.
The expression should follow the syntax for Java regular expressions. For more information about this syntax, see the Foglight Command-Line Reference Guide. The default expression, AMQ\..*|MQMON\..*|CSQ\..*, matches any objects whose names start with AMQ., MQMON., or CSQ..
For example:
To expand the expression to select objects whose names start with TEMP., edit the expression as follows:
AMQ\..*|MQMON\..*|CSQ\..*|TEMP\..*
To monitor only objects whose names start with QUEST (that is, to exclude all objects not beginning with QUEST):
a
Deactivate the MQ Agent.
b
Set the Exclude Objects Regex value to: ^(?!QUEST).* and save your changes.
c
Clear the queue and the channel list.
d
Start the MQ Agent.
11
In the display area, click Save.
12
To set the performance, channel, queue manager, and configuration events, see Event properties.
Otherwise, click Back to Agent Status and activate the MQ Agent, as described in Activating MQ Agent instances and starting data collection .

Event properties

Use the Event Settings agent properties for an MQ Agent to configure the monitoring of the following event types:
•
Performance events
•
Channel events
•
Queue manager events

Performance events

To set performance event properties:
1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
2
On the Agent Status dashboard, select the instance of the MQ Agent whose properties you want to modify and click Edit Properties.
3
Locate the Event Settings properties.
4
Select the Performance Events option: True or False.
Select True if you want the MQ Agent to monitor performance events. Otherwise, select False.
5
Select the Consume Performance Event Message option: True or False.
 
* 
NOTE: This agent property requires a get permission on this queue. This permission is set on the IBM WebSphere MQ Server.
•
Select True if you want the MQ Agent to remove performance events from the SYSTEM.ADMIN.PERFM.EVENT queue as they are read.
or
•
Select False if you want the MQ Agent to retain performance events in the SYSTEM.ADMIN.PERFM.EVENT queue as they are read.
When this option is set to False, the MQ Agent does not consume any events in event queues. With no other means to remove event messages from the event queues, the event queues become full, and the corresponding event collection does not work.
6
Click Performance Event List, and select the performance event list that you want to use.
7
Optional — Clone the selected performance event list.
a
Click the Clone button to the right of Performance Event List.
b
In the dialog box that opens, type a name for the cloned list.
8
Update the performance event list.
a
Click the Edit button to the right of Performance Event List.
A dialog box opens, listing the available performance events, and indicating if they are enabled. The MQ Agent includes the following performance events:
 
Table 6. Performance events
Performance Event
Description
Queue Depth High
The queue depth is incremented to or above the specified limit.
Queue Depth Low
The queue depth is decremented to or below the specified limit.
Queue Depth Full
The queue contains the maximum number of messages.
Queue Service Interval High
No successful get operations or MQPUT calls have been detected within an interval greater than the specified limit.
Queue Service Interval OK
A successful get operation has been detected within an interval less than or equal to the specified limit.
b
In the dialog box, click Add Row to add an entry.
For each row, define the following values:
Performance Event: Type the name of the performance event.
Monitor: Select the check box to enable the monitoring of this event, or clear the check box to disable monitoring.
c
Click Save Changes in the dialog box. The dialog box closes.
9
In the display area, click Save.

Channel events

To set channel event properties:
1
Locate the Event Settings properties.
2
Select the Channel Events option: True or False.
•
Select True if you want the MQ Agent to monitor channel events. Otherwise, select False.
3
Select the Consume Channel Event Message option: True or False.
 
* 
NOTE: This agent property requires a get permission on this queue. This permission is set on the IBM WebSphere MQ Server.
•
Select True if you want the MQ Agent to remove channel events from the SYSTEM.ADMIN.CHANNEL.EVENT queue as they are read.
or
•
Select False if you want the MQ Agent to retain channel events in the SYSTEM.ADMIN.CHANNEL.EVENT queue as they are read.
When this option is set to False, the MQ Agent does not consume any events in event queues. With no other means to remove event messages from the event queues, the event queues become full, and the corresponding event collection does not work.
4
Click Channel Event List, and select the channel event list that you want to use.
5
Optional — Clone the selected channel event list.
a
Click the Clone button to the right of Channel Event List.
b
In the dialog box that opens, type a name for the cloned list.
6
Update the newly-selected channel event list.
a
Click the Edit button to the right of Channel Event List.
A dialog box opens, listing the available channel events, and indicating if they are enabled. The MQ Agent includes the following channel events:
 
Table 7. Channel events
Channel Event
Description
Bridge Started (z/OS only)
The IMS bridge is started.
Bridge Stopped (z/OS only)
The IMS bridge is stopped.
Channel Activated
A channel that is waiting to become active, and for which a Channel Not Activated event is generated, can become active, because an active slot has been released by another channel.
Channel Auto Definition Error
The automatic definition of a channel failed.
Channel Auto Definition OK
The automatic definition of a channel is successful.
Channel Conversion Error
A channel is unable to carry out data conversion.
Channel Not Activated
A channel is required to become active, either because it is starting, or because it is about to make another attempt to establish connection with its partner. However, the limit on the number of active channels is reached, which prevents the channel from becoming activated.
Channel SSL Error
A channel using Secure Sockets Layer (SSL) or Transport Layer Security (TLS) fails to establish a connection.
Channel Started
Either an operator issued a Start Channel command, or a channel is successfully established.
Channel Stopped
A channel is stopped.
Channel Stopped By User
A channel is stopped when a user issues a STOP CHL command.
b
In the dialog box, click Add Row to add an entry.
For each row, define the following values:
Channel Event: Type the name of the channel event.
Monitor: Select the check box to enable the monitoring of this event, or clear the check box to disable monitoring.
c
Click Save Changes in the dialog box.
The dialog box closes.
7
In the display area, click Save.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating