WebSphere MQ tagging

AppMon provides the capability to follow transactions through WebSphere MQ queue managers. As the page title implies you don't need to instrument the queue manager with a separate Sensor or Agent ‐ as is the case with other messaging. You just have to make sure the application that PUTs and the application that GETs are both instrumented by an Agent that supports MQ tagging. The following agents provide Sensors for MQ tagging:

  • Java Agent: MQSeries Sensor to tag outgoing messages, MQ Receive Entry Point Sensor to start new PurePaths for incoming messages.
  • .NET Agent: .NET MQSeries Sensor to tag outgoing messages, .NET MQ Receive Entry Point Sensor to start new PurePaths for incoming messages.
  • WebSphere Message Broker Agent ‐ No extra sensor needs to be placed.
  • CICS Agent: The CICS Sensor is automatically configured to start new PurePaths for any incoming messages.

Configuration

Note

This is not a Sensor in a System Profile, but an AppMon Server setting.

The Settings > Dynatrace Server > MQ Tagging settings specify what information should be used to identify WebSphere MQ messages. This information is used to link the subpaths from the client to the server side for applications that use MQ. The tagging always uses the MQ message ID. The correlation ID, the queue manager name, and the queue name can be added, as shown in the figure.

The default setting uses the message ID and the correlation ID for tagging. This setting does not require any additional configuration.

If the message ID of the MQ messages is unique within your environment, it is not necessary to add any additional information for tagging.

If the message ID is not unique within your environment (for example, if an application reads a message, processes it, and puts its contents to another queue with the same message ID), additional information is required for tagging. Otherwise, paths might be linked together incorrectly. The AppMon Server log file contains a message that indicates the problem.

The following log messages indicate that the custom tags are not unique.

WARNING [ExecPath] Invalid subPath count on synchronous link node: 2, link added by sensor: Java Web Requests
WARNING [com.dynatrace.diagnostics.server.datacenter.i] Cyclic path references detected: custom tag probably not unique: ...
WARNING [com.dynatrace.diagnostics.server.datacenter.i] Failed to link root paths: custom tag probably not unique: ...

If your environment requires using the queue or queue manager names to uniquely identify messages, you might need to set up WebSphere MQ Mapping.