> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Monitoring for IBM WebSphere MQ

> 📊 Configure GermainUX to collect and analyze IBM WebSphere MQ queue health and performance metrics.

Components
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler)
[`Mobile App`](https://docs.germainux.com/main/germain-ux-mobile-app)
[`RPA Bot Recorder`](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder)
[`RUM JS`](https://docs.germainux.com/main/germain-ux-rum-js)

Availability
2015.4

> **[11. Configure SLAs](#11-configure-slas)**
>
> Per-queue threshold examples

> **[12. Configure Rules](#12-configure-rules)**
>
> Detect combined queue conditions

> **[13. Configure Alerts and Watches](#13-configure-alerts-and-watches)**
>
> Notify on queue problems

> **[Troubleshooting](#troubleshooting)**
>
> Resolve MQ setup issues

**Configuring Monitoring for IBM WebSphere MQ with GermainUX**

📊 Configure GermainUX to collect and analyze IBM WebSphere MQ queue health and performance metrics.

## 1. Open the Monitor Server Wizard

Go to:

**Germain Workspace > Left Menu > Setting > Wizards > Monitor Server**

Create a new monitoring component.

![Configure Monitoring for IBM WebSphere MQ: 1. Open the Monitor Server Wizard](https://mintcdn.com/germain-ux/ZJflvRMC808oZDAs/images/main/configure-monitoring-for-ibm-websphere-mq/image-20260908-231513.png?fit=max\&auto=format\&n=ZJflvRMC808oZDAs\&q=85\&s=629210f1238a0b4bcc94bbba8f172aa0)

## 2. Select the Node and Engine

Select the GermainUX Node and Engine that will execute the MQ monitor.

Choose an Engine that:

* Can access the IBM WebSphere MQ environment
* Can establish the required SSH connection when using remote monitoring
* Has access to the required credentials
* Can communicate with GermainUX

## 3. Select the WebSphere MQ Monitor

Select the applicable:

**WebSphere MQ Monitor**

Choose the appropriate monitoring configuration for your deployment.

GermainUX supports:

* WebSphere MQ Monitor — Local
* WebSphere MQ Monitor — SSH

## 4. Configure Local or Remote Monitoring

### Local

Use the local monitor when the monitoring component has direct access to the IBM WebSphere MQ server.

Configure the required MQ server and monitoring information.

### SSH

Use the SSH monitor when the GermainUX Engine connects remotely to the IBM WebSphere MQ server.

Configure the required:

* Server
* SSH connection
* Credentials
* MQ monitoring settings

## 5. Configure the MQ Environment

Populate the remaining fields required by the WebSphere MQ Monitor.

Depending on the monitor configuration, identify the applicable:

* MQ server
* Queue manager
* Queue
* Environment
* Monitoring component

Use descriptive names so the monitored MQ resources can be clearly identified in dashboards, alerts, and reports.

## 6. Configure Monitoring Frequency

Configure how frequently GermainUX should collect MQ metrics.

Choose a frequency appropriate for:

* Queue criticality
* Message-processing rate
* Required detection time
* Environment
* Monitoring overhead

Critical queues may require more frequent monitoring than low-volume or non-production queues.

## 7. Configure Queue Depth Monitoring

Monitor:

**WebSphere MQ Queue Depth**

Queue Depth represents the number of messages currently waiting in the queue.

Use it to detect:

* Message backlog
* Queue congestion
* Unexpected increases
* Sustained queue growth

## 8. Configure Queue Time Monitoring

Monitor:

**WebSphere MQ Queue Time**

Use Queue Time to identify messages that are taking longer than expected to be processed.

Analyze Queue Time together with Queue Depth to distinguish normal workload increases from processing degradation.

## 9. Configure Oldest Message Monitoring

Monitor:

**WebSphere MQ Oldest Message**

This KPI identifies the age of the oldest message waiting in the queue.

It can help identify:

* Stuck messages
* Consumer problems
* Processing delays
* Queues that are no longer draining normally

## 10. Configure MQ Event Monitoring — Optional

When WebSphere MQ server-log monitoring is configured, use:

**WebSphere MQ Event**

to analyze events detected in the MQ server logs.

Use log events together with Queue Depth, Queue Time, and Oldest Message to provide additional diagnostic context.

## 11. Configure SLAs

Configure thresholds appropriate for each queue.

Examples include:

### Queue Depth

`Queue Depth > Expected Threshold`

### Queue Time

`Queue Time > Expected Threshold`

### Oldest Message

`Oldest Message Age > Expected Threshold`

Avoid applying identical thresholds to every queue.

Thresholds should reflect:

* Normal message volume
* Expected processing rate
* Queue purpose
* Business criticality
* Time sensitivity

## 12. Configure Rules

Use GermainUX Rules to detect more meaningful combinations of MQ conditions.

Examples:

**Queue Depth Increasing + Queue Time Increasing**

Potential processing bottleneck.

**Queue Depth Increasing + Oldest Message Increasing**

Potential consumer or downstream issue.

**Oldest Message Increasing Continuously**

Potential stuck message.

**Queue Backlog + Application Error**

Potential application processing failure.

**Queue Performance Degradation + Infrastructure Issue**

Potential dependency or resource problem.

## 13. Configure Alerts and Watches

Configure notifications for MQ conditions requiring attention.

Examples:

**Critical Queue Depth Above Threshold → Alert Integration Team**

**Oldest Message Above SLA → Notify Application Support**

**Queue Time Increasing → Notify MQ Operations**

**Sustained Queue Backlog → Trigger Diagnostic Workflow**

GermainUX can trigger:

* Alerts
* Watches
* Reports
* Approved diagnostics
* Approved automation

## 14. Configure Dashboards

IBM WebSphere MQ monitoring data is available under:

**Monitoring > IT > Application > IBM > WebSphere MQ**

Use dashboards to analyze:

* Queue Depth
* Queue Time
* Oldest Message
* MQ Events
* Historical trends
* SLA violations

Analyze individual queues and compare behavior across monitored MQ resources.

## 15. Correlate MQ with Other Technologies

When GermainUX monitors related systems, correlate MQ activity with:

* Java applications
* Application servers
* Operating systems
* Databases
* APIs
* Network
* Logs

For example:

**Queue Backlog → Consumer Application Error**

or:

**Queue Time Increase → Downstream Database Slowdown**

This can help identify the system responsible for the observed MQ condition.

## 16. Validate the Configuration

After configuration, verify:

**1. MQ Monitor is enabled**

**2. Selected Engine is online**

**3. Local or SSH connectivity succeeds**

**4. MQ environment is accessible**

**5. Queue Depth is collected**

**6. Queue Time is collected**

**7. Oldest Message is collected**

**8. MQ Events are available when configured**

**9. Data appears in the WebSphere MQ dashboard**

**10. SLAs evaluate correctly**

**11. Alerts and Watches operate as expected**

## Troubleshooting

### No MQ Data

Verify:

* Engine is online.
* MQ Monitor is enabled.
* Correct Engine is selected.
* MQ server is accessible.
* Monitoring credentials are valid.
* Monitoring account has sufficient permissions.

### SSH Monitor Cannot Connect

Verify:

* MQ server hostname
* SSH port
* Firewall
* Network routing
* Username
* Authentication
* Monitoring permissions

### Local Monitor Does Not Collect Data

Verify:

* Monitoring component is operational.
* MQ environment is accessible locally.
* Monitoring account has the required permissions.
* Correct MQ Monitor is configured.

### Queue Metrics Are Missing

Verify:

* Correct MQ environment is selected.
* Queue is accessible to the monitor.
* Monitoring component executes successfully.
* Required permissions are available.

### Data Appears but Alerts Do Not Trigger

Verify:

* SLA is enabled.
* Correct KPI is selected.
* Threshold is appropriate.
* Rule conditions are satisfied.
* Watch or alert configuration is enabled.

### Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your WebSphere environment.

[Contact GermainUX Support](https://docs.germainux.com/main/support.md).

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> The Germain Team can help you set this up.

> **Can't find what you need?**
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.