Monitoring IBM MQ
IBM MQ is a messaging middleware that enables communication between applications across diverse platforms reliably and asynchronously. Instana comprehensively monitors IBM MQ instances to identify bottlenecks and optimize their performance.
Instana collect metrics and trace message flows within IBM MQ by using the IBM MQ sensor and tracer. After you install the Instana agent, the IBM MQ sensor is installed automatically. Depending on your environment, you need to configure the sensor. The sensor then periodically polls the metrics and sends them to the Instana backend for visualization and alerting.
IBM MQ Tracer traces IBM MQ messages. It uses an IBM MQ user exit to gather tracing data, which is reported to either the local or a remote host agent. IBM MQ Tracer support both on-premises and containerized IBM MQ deployments on Red Hat OpenShift clusters.
Prerequisites
Before you set up monitoring for IBM MQ, complete the following prerequisites:
- Install the Instana agent.
- Check support information to ensure compatibility.
- Understand the basic IBM MQ monitoring concepts, including connection modes, privileged users, and monitoring methods.
- Review the IBM MQ monitoring scenarios.
- If the Instana agent is installed by using a nonprivileged user to connect to the queue manager, grant the necessary authorities.
Setting up IBM MQ monitoring
After you install the Instana agent, the IBM MQ sensor is automatically installed.
To enable IBM MQ monitoring, complete the following steps:
-
Note: Depending on your deployment setup, the sensor configuration might differ.
To configure IBM MQ monitoring based on your environment, see the following topics:
-
Optional: To collect specific metrics from IBM MQ, configure additional settings.
Viewing metrics and traces
After you set up monitoring, you can view the metrics and traces that are related to IBM MQ in the Instana UI. For more information, see Viewing traces and metrics.
Troubleshooting
You might encounter issues related to IBM MQ connection and authority. For more information, see Troubleshooting.