IBM MQ Agent Configuration

The Nodinite IBM MQ Monitoring Agent provides unified monitoring and logging capabilities from a single agent installation. On this page, you will learn how to:

✅ Access remote configuration for the IBM MQ Monitoring Agent
✅ Configure global settings (Environment, Allowed Hosts, Log Level)
✅ Manage secrets and certificates for secure operations
✅ Enable AI Diagnostics for intelligent troubleshooting
✅ Navigate to Monitoring and Logging configuration pages

Note

Before you can configure the IBM MQ Monitoring Agent, you must install it and create an initial Monitoring Agent Configuration. If you're new, start here.

Understanding the Unified Agent Architecture

The IBM MQ Monitoring Agent provides two complementary capabilities in a single installation:

1. Monitoring – Real-Time State Visibility

• What: Current queue depths, message age, channel status, listener availability
• Purpose: Proactive alerting when thresholds are breached (queue backlog, channel failure, listener down)
• Configuration: Configuration - Monitoring (spoke page)
• Conceptual Overview: Monitoring IBM MQ

2. Logging – Historical Transaction Traceability

• What: IBM Monitoring Events from Integration Bus/ACE workflows with full payloads and context values
• Purpose: End-to-end transaction tracking, compliance auditing, business intelligence
• Configuration: Configuration - Logging (spoke page)
• Conceptual Overview: IBM Integration Bus Logging

The unified architecture showing Monitoring and Logging capabilities in a single agent.

The diagram above illustrates how the unified IBM MQ Monitoring Agent handles both monitoring (real-time state) and logging (historical transactions) from a single agent installation.

Remote Configuration

As a Nodinite Administrator, click the 'Configuration' button to open the remote configuration modal and configure the agent settings, monitoring, and logging.

Click the 'Configuration' button to open the configuration dialog for the agent.

You can also apply specific configurations directly on the Resource using the Action button, provided your Monitor View has the Remote Actions feature enabled.

Configuration Navigation

The IBM MQ Agent configuration is organized into three main areas:

Settings Tab (This Page)

Configure global agent settings:

• Environment
• Allowed Hosts
• Log Level
• Secret Management
• AI Diagnostics

Monitoring Configuration

Configure queue managers, queues, channels, listeners, thresholds, and filters:

• Configuration - Monitoring (dedicated page)

Logging Configuration

Configure IBM Integration Bus/ACE Monitoring Event logging:

• Configuration - Logging (dedicated page)

Settings Tab

Within the Settings tab, provide details that determine how the IBM MQ Monitoring Agent operates.

Example: Settings tab for IBM MQ Agent configuration.

Environment

Set the name of the target environment (for example, DEMO, TEST, QA, PROD). This feature is standard for all Monitoring Agents.

Allowed Hosts

Specifies which host headers are accepted by the application. Use * to allow all hosts, or provide a semicolon-separated list of allowed hostnames (e.g., example.com;*.example.com). This is a security feature to prevent host header attacks.

Log Level

Select the logging level for the agent (e.g., Error, Warning, Information, Debug). This is used for diagnostics logs.

Secret Management

^{New 7.1}

For comprehensive guidance on securing sensitive data and managing certificates for the Nodinite IBM MQ Monitoring Agent, see Secret Management with Automatic Certificate Handling.

This includes:

• ✅ Automated certificate generation and lifecycle management
• ✅ Encryption of sensitive configuration data (connection strings, API keys, passwords)
• ✅ Service account password change support (v7+)
• ✅ Certificate expiration monitoring and auto-renewal

AI Diagnostics

^{New 7.0.4}

Example: AI Diagnostics tab for IBM MQ Queue Manager configuration.

Enable AI Diagnostics to automatically analyze errors and warnings from monitored IBM MQ queue managers and queues. When issues occur, AI Diagnostics provides intelligent root cause analysis and actionable recommendations to accelerate troubleshooting.

Tip

Learn more about configuring and using AI-powered diagnostics in the AI Diagnostics documentation.

Add IBM MQ Monitoring Agent Configuration

After you install the IBM MQ Monitoring Agent, provide Nodinite with connection details so the Monitoring Service can detect the new agent.

No one can monitor or configure the IBM MQ Monitoring Agent until you complete the steps below.

Configuration Steps

1. Add and configure a new Monitoring Agent Configuration
   • Find connection information in the README.txt file in the installation folder
2. Use the Remote Configuration feature to configure the agent settings (this page)
3. Configure monitoring for queue managers: Configuration - Monitoring
4. (Optional) Configure logging for IBM Integration Bus events: Configuration - Logging
5. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the IBM MQ Monitoring Agent according to your business needs
   • Add or manage Monitor View
6. Fine-tune specific settings directly on Resources using Remote Actions

Frequently Asked Questions

Use the troubleshooting guide to find the FAQ and answers to known problems.

Next Step

Configuration - Monitoring – Set up queue managers, thresholds, filters, and SSL
Configuration - Logging – Set up logging for IIB/ACE workflows
Add or manage a Monitoring Agent Configuration
Add or manage Monitor View

Related Topics

Monitoring IBM MQ – Understand queue state evaluation and alert generation
Managing IBM MQ – Learn how to purge queues and perform remote management operations
Install IBM MQ Monitoring Agent
Update
Monitoring Agents
Applications