Monitoring coverage
Which IBM MQ setups work
Collection methods
Local and remote MQ monitoring
Configuration
Set up IBM MQ monitoring
Deployment and configuration
Versions, permissions and depth
Business outcomes
Monitoring coverage
Monitoring availability depends on the IBM MQ version, operating system, enabled administrative interfaces, permissions, and GermainUX configuration.Queue managers
GermainUX can monitor:- Queue-manager availability and operating status
- Queue-manager uptime
- Local and remote connectivity
- Command execution failures
- Connection and authentication problems
- Queue-manager errors detected in accessible logs
- Repeated stops, starts, or unexpected status changes
Queues and messages
Thresholds should be configured for each queue according to its normal workload and business purpose. A queue depth of zero may be expected for one queue, while a persistent backlog may be normal for another.
Channels and listeners
Depending on the configured monitoring access, GermainUX can monitor:- Channel status
- Sender and receiver channel availability
- Repeated channel retries
- Stopped or inactive channels
- Connection failures
- Listener availability
Show all 9
Show all 9
- Transmission-queue depth
- Last message or channel activity
- Channel errors found in IBM MQ logs
Logs and errors
Configure File and Log Monitoring for accessible IBM MQ error and operational logs. GermainUX can detect and categorize events such as:- Queue-manager startup or shutdown failures
- Channel and listener errors
- Queue-full conditions
- Authentication and authorization failures
- Connection failures
- Undelivered messages
Show all 10
Show all 10
- Disk and filesystem problems
- Damaged objects or recovery problems
- Repeated warning or error codes
- Unusual changes in error volume
Infrastructure
Extend IBM MQ monitoring to its supporting environment using:
Relevant infrastructure metrics can include:
- CPU and memory utilization
- Disk and filesystem capacity
- Network connectivity
- IBM MQ processes
- Container and pod health
- Process restarts
- File-descriptor and connection limits
Collection methods
The GermainUX Engine supports local and remote IBM MQ monitoring.Local monitoring
Use local monitoring when the GermainUX Engine runs on the IBM MQ server and has permission to execute the required IBM MQ status and administrative commands.Remote monitoring through SSH
Use SSH monitoring when the GermainUX Engine runs on another server. The configured account must:- Be authorized to connect to the IBM MQ server
- Have only the permissions required to execute approved monitoring commands
- Have read-only access wherever possible
- Be protected according to the organization’s credential-management requirements
Logs and external metrics
IBM MQ data can also be collected from:- Accessible IBM MQ logs
- Customer-provided scripts
- Authorized administrative endpoints
- Prometheus-compatible metrics when an appropriate IBM MQ exporter is deployed
- Infrastructure and container platforms
- Application and integration telemetry
Business-process correlation
IBM MQ typically supports transactions spanning multiple applications and integrations. GermainUX can correlate messaging conditions with other monitored activity when the required identifiers and data sources are available. Examples include:- Order submitted but not processed
- Payment request delayed in a queue
- Reservation message not consumed
- Customer update waiting for a downstream system
- Integration failure associated with a stopped channel
- Business-process delay associated with increasing message age
- Application errors occurring during an IBM MQ incident
Analytics and outlier detection
GermainUX Analytics and outlier detection can identify:- Unusual increases in queue depth
- Abnormal message age
- Changes in producer or consumer activity
- Repeated queue-manager or channel instability
- New IBM MQ errors
- Resource patterns associated with messaging degradation
- Queues behaving differently from their historical baseline
- Relationships between IBM MQ degradation and application or business-process failures
Alerts
Configure alerts for conditions such as:- Queue manager unavailable
- Queue depth above an approved threshold
- Queue approaching maximum capacity
- Oldest message exceeding its processing SLA
- Dead-letter queue receiving messages
- Channel or listener unavailable
Show all 11
Show all 11
- Repeated channel retries
- Authentication or connection failures
- IBM MQ errors detected in logs
- Disk or filesystem capacity risk
- Failed synthetic messaging transaction
Automated actions
GermainUX Automation can execute customer-defined and approved actions, including:
Actions that start or stop queue managers, channels, listeners, or other IBM MQ resources must be explicitly authorized, tested, and protected by appropriate operational controls. Avoid automated actions that could interrupt message processing or cause duplicate transaction execution.
Configuration
Prerequisites
Before configuring IBM MQ monitoring:1
Identify the queue managers, queues, channels, listeners, and logs to monitor
2
Document the expected workload and availability requirements
3
Select local or remote monitoring
4
Create a least-privilege monitoring account
5
Confirm that the GermainUX Engine can access the IBM MQ server
6
Identify the applications and business processes that depend on IBM MQ
7
Define which identifiers may be collected for correlation
8
Identify maintenance and batch-processing schedules
Configure the monitor
In GermainUX:- Go to Workspace > Settings > Wizards.
- Select Monitor Server.
- Select the monitoring node and GermainUX Engine.
- Select the applicable IBM MQ Monitor:
- IBM MQ Monitor—Local
- IBM MQ Monitor—SSH
- Select or create the monitored IBM MQ server.
- Select the required credentials for remote monitoring.
- Enter the queue-manager and monitoring configuration.
- Select the queues, channels, or objects to monitor.
- Configure the execution schedule and timeout.
- Review and submit the monitor.
- Confirm that the component is running and producing data.
Configure KPIs and SLAs
Configure KPIs and SLAs for the IBM MQ objects important to the environment.
Use queue-specific thresholds rather than applying the same threshold to every queue.
Validate the configuration
After deployment:1
Confirm that every expected queue manager is visible
2
Verify queue depth against an authorized IBM MQ administrative view
3
Confirm that oldest-message age and queue time are interpreted correctly
4
Validate channel and listener status
5
Confirm that IBM MQ logs are being read from the correct locations
6
Verify host or container telemetry when configured
7
Generate a controlled test message and confirm that the expected metrics change
8
Test alerts using safe thresholds or a non-production environment
9
Verify application and business-process correlation
10
Confirm that maintenance periods suppress expected operational alerts
Security considerations
- Use a dedicated, least-privilege monitoring account.
- Prefer read-only administrative access.
- Protect SSH keys, passwords, and IBM MQ credentials in GermainUX credential storage.
- Restrict network access to the required IBM MQ and SSH endpoints.
- Do not collect message payloads unless explicitly required and approved.
- Mask or exclude sensitive message identifiers and attributes.
Show all 9
Show all 9
- Review logs for personal, financial, authentication, or regulated information.
- Limit automated actions to approved commands and resources.
- Audit changes to IBM MQ monitoring and automation configuration.
Deployment and configuration
- Deploy or select a GermainUX Engine with access to the IBM MQ environment.
- Select local monitoring or remote monitoring through SSH.
- Configure the queue managers, queues, channels, listeners, and service windows to monitor.
- Configure File and Log Monitoring for accessible IBM MQ logs.
- Configure the applicable AIX, Linux, Windows, Docker, Kubernetes, and network monitoring.
- Define queue-specific KPIs and SLAs for depth, utilization, message age, processing time, availability, and errors.
Show all 11
Show all 11
- Configure automated analytics and outlier detection.
- Correlate IBM MQ conditions with dependent applications, integrations, and business processes.
- Configure alerts, incident integrations, and approved automated actions.
- Define maintenance windows for planned IBM MQ, application, and infrastructure changes.
- Validate collection, thresholds, alerts, correlations, and automation in a safe environment.
Get More Information
GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your WebSphere environment. Contact GermainUX Support.Get Help
Contact GermainUX Support
The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.
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.