Dynatrace OneAgent traces IBM MQ messages in your applications.
- Out of the box, Dynatrace OneAgent traces IBM MQ messages in your applications as described below.
- Install an IBM MQ extension to retrieve IBM MQ metrics and automatically retrieve the queue topology.
IBM MQ message tracing
Dynatrace OneAgent displays IBM MQs in the Smartscape topology view.
Example smartscape topology
All services that use an IBM MQ are listed in the Sends to queue and Receives from queue sections of the related service overview page.
Example service overview
As long as each message is sent and received within the same queue, you get an end-to-end view of each message trace.
Example end-to-end view
Service-level backtraces can follow messages backward to their origins.
Example service-level backtrace
When you look at a single PurePath, you can understand the end-to-end flow of the message.
Tracing of alias, remote, and cluster queues
Dynatrace needs to know the alias, remote, and cluster queues that you're using in order to connect the services to an end-to-end trace.
You can define alias, remote, and cluster queues via the IBM MQ tracing API (see queue managers).
Alternatively, you can use the IBM MQ extension to automatically retrieve the queue topology from your environment:
- Enable Retrieve queue topology for improved transaction tracing in the IBM MQ extension.
- Provide the API endpoint and API token key.
- Save the changes.
- See CICS, IMS and MQ monitoring for tracing requirements of IMS MQ Bridge queues on z/OS.