Monitoring IBM MQ
Summary: Nodinite's IBM MQ Monitoring Agent provides real-time visibility, proactive alerts, and actionable insights for your IBM MQ landscape. This page explains how monitoring works, how to detect issues, and how to use management actions to resolve them. For management features and remote actions, see Managing IBM MQ.
Gain real-time visibility and proactive control over your IBM MQ landscape with the Nodinite IBM MQ Monitoring Agent. Instantly detect issues, automate alerts, and empower every user to take action—no complex setup required.
| Category | Monitors |
|---|---|
| Queues | What is being Monitored for IBM MQ queues? |
| Listeners | What is being Monitored for IBM MQ Listeners? |
| Queue Managers | What is being Monitored for IBM MQ Queue Managers? |
| Client Connections | What is being Monitored for IBM MQ Client Connections? |
| Channels | What is being Monitored for IBM MQ Channels? |
What is being Monitored for IBM MQ queues?
The Nodinite IBM MQ Monitoring Agent evaluates queues by user-defined thresholds. Checks are performed on availability and the number of messages on the queue(s). Also, the maximum age of the first message on each queue is analyzed. An administrator can change thresholds per queue manager and related settings.
On this page, you will:
- ✅ Monitor queues, channels, listeners, and queue managers with actionable insights
- ✅ Detect bottlenecks and automate alerts to minimize downtime
- ✅ Empower users with Remote Actions and self-service management
- ✅ Ensure seamless system integration and business continuity
The Nodinite IBM MQ Monitoring Agent enables you to monitor IBM MQ queues, channels, and more. Set thresholds for message count and age, receive instant alerts, and take remote actions to keep your system healthy and efficient.
Typical Workflow:
- Monitor IBM MQ resources and receive automated alerts for issues (this page)
- Use management features and remote actions (Managing IBM MQ) to resolve problems directly from the monitoring view
- All actions are logged for compliance and audit
Role-Based Access: With Nodinite, you control who can monitor, manage, and resolve MQ issues. Assign permissions to support, operations, and business teams for secure, tailored access. See User access to IBM MQ monitoring for details.
For a full list of available remote actions and management features, see the Managing IBM MQ page.
How Monitoring and Management Work Together:
- Monitoring detects issues and provides actionable alerts (this page).
- Management enables users to resolve issues using secure remote actions (Managing IBM MQ).
- All actions are logged for compliance and audit.
- Role-based access ensures only authorized users can take action.
- State of the queues - Makes sure the queues have the intended run-time state
- Get/Put inhibited check
- Alias queue targets a queue (base queue name property is set)
- Access checks - Makes sure queues stay available and accessible
- Access rights - Makes sure no one tampers with access rights
- Service available - If Nodinite can't check the state of your queues, chances are no one else can use them either
- Global settings, overridable per queue
- Age verification
- Count (warning/error)
- Quota-evaluation
- Dead letter
List of queues in a Nodinite self-service Monitor View.
One single queue will be displayed within Nodinite as one Resource. If you have 42 queues, then you will have 42 Resources in Nodinite.
- All queues depending on type in MQ belong to either the 'Local Queue', 'Model Queue', 'Alias Queue' or 'Remote Queue' category.
Here's an example of IBM MQ categories - The Application name is based on the display name for the queue manager.
- Display name for queue manager
Here's an example of display name for queue manager as Application name
- Display name for queue manager
State evaluation for Queues
Each queue (Resource) can have one of the following states at any given moment:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available |
|
Review prerequisites | |
| Error | Not operational |
|
- | |
| OK | Operational |
|
- |
Example of a queue that is not available (the queue manager is not reachable)
From within Nodinite, you can reconfigure the state evaluation on the Resource level using the Expected State feature.
Important
If the queue has get inhibited then the age of messages cannot be evaluated.
Alert history for queues
During root cause analysis or other purposes, it might be helpful to understand how often problems with queues happen. If your Monitor View allows it, you can search for historical state changes for the provided timespan either for all queues or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
 Search for alert history for all resources in the Monitor View |
 Alert history for the selected queue |
What is being Monitored for IBM MQ Listeners?
The IBM MQ Monitoring Agent evaluates Listeners by hardcoded thresholds. Checks are performed on the state.
- State of the Listener - Makes sure the Listener has the intended run-time state
State evaluation for listeners
Each listener (Resource) can have one of the following states at any given moment:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available |
|
Review prerequisites | |
| Error | Stopped |
|
- | |
| OK | Started |
|
- |
From within Nodinite, you can reconfigure the state evaluation on the Resource level using the Expected State feature.
What is being Monitored for IBM MQ Queue Managers?
The IBM MQ Monitoring Agent evaluates Queue Manager by evaluating general connectivity. Checks are performed on the availability of the service.
- Available State of the Queue Manager - Makes sure the Queue Manager is accessible
State evaluation for queue manager
Each Queue Manager (Resource) can have one of the following states at any given moment:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available |
|
Review prerequisites | |
| OK | Started |
|
- |
From within Nodinite, you can reconfigure the state evaluation on Resource level using the Expected State feature.
What is being Monitored for IBM MQ Client Connections?
A Client Connection is a channel of type Client. See the next bullet for additional information.
What is being Monitored for IBM MQ Channels?
The Nodinite IBM MQ Monitoring Agent evaluates Channels by hardcoded thresholds. Checks are performed on the state of the channel.
- State of the Channels -Ensure the Channels have the intended run-time state
State evaluation for channels
Each channel (Resource) can have one of the following states at any given moment:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available |
|
Review prerequisites | |
| Error | Stopped |
|
- | |
| OK | Started |
|
- |
From within Nodinite, you can reconfigure the state evaluation on Resource level using the Expected State feature.
Frequently asked questions
Use the troubleshooting guide to find the FAQ and answers to known problems.
How do monitoring and management work together? Monitoring detects issues and provides actionable alerts (this page). Management enables users to resolve those issues using secure remote actions. See Managing IBM MQ for details.
How do I grant users access to IBM MQ monitoring and management? See User access to IBM MQ monitoring for details on permissions and role-based access.
How do I resolve issues detected during monitoring? Use management features and remote actions (Managing IBM MQ) to resolve problems directly from the monitoring view. All actions are logged for compliance.
How do I enable monitoring and management for IBM MQ? Enable monitoring of one or more IBM MQ Queue Managers as described in the Configuration page. Then use the management features on the Managing IBM MQ page to take action.
Next step
Managing IBM MQ – See management features and remote actions User access to IBM MQ monitoring