The health of the IBM Websphere MQ monitor is not affected by default, if the listener status is stopped.
- The health of the listener will not be affected unless the threshold is configured for the status attribute under Listener monitoring. You have to configure a threshold for status manually so that the health status of the listener is affected.
- To trigger an alert, configure a threshold such that the severity is 'Critical' if status changes to "STOPPED".
New to ADSelfService Plus?
Related Articles
Inactive channels are not getting listed in IBM Websphere MQ monitor
Inactive channels are not displayed in the IBM Websphere MQ monitor page by default. You can configure them by following the below steps : In the monitor home page, go to Monitor Options -> Edit Monitor. In the Edit Monitor page, enable the Filter ...
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...
Channel status is shown as STOPPED even after the channel is restarted
Below are the behaviours of IBM Websphere MQ and Applications Manager : If a channel is started, the status of the channel is not changed to RUNNING. It will be in INACTIVE state until a connection is made to the channel and a get / put is ...
Queues and channels data are not collected in IBM Websphere MQ monitor
Check if monitoring parameter is enabled for Queues and Channels. Run the following command to get the status of queues and channels, DISPLAY QSTATUS(<QUEUE_NAME>) ALL DISPLAY CHSTATUS(<CHANNEL_NAME>) ALL From the output, check ...
Prerequisites for adding IBM MQ monitor via SSL
To add the IBM monitor via SSL, please follow the required steps given below with respect to authentication type: SSL Authentication is optional (One-way SSL) If SSL Authentication is optional (One-way SSL), you need to load the MQ server's CA ...