Dynatrace automatically detects how messages are processed within your environment. Under certain circumstances, however, some manual configuration is needed to allow Dynatrace to detect how messages are processed.
Review the following table to determine whether some manual configuration is needed.
If this is true…
…then this manual configuration is needed
The application uses non-standard or non-event-based message queue handlers.
Define a custom messaging service.
You're using IBM MQ.
Define your IBM MQ configuration in Dynatrace to get a continuous service flow.
The messaging client isn't compatible with Dynatrace, or you're using an unsupported protocol.
Extend the traces with OpenTelemetry or OneAgent SDK (see also OneAgent SDK on GitHub).
OneAgent version 1.250+ Dynatrace uses the IBM MQ queue manager name to detect and group IBM MQ processes. To manage the IBM MQ process group detection
Go to Settings > Processes and containers > Built-in detection rules and find Group IBM MQ processes by queue manager name.
Via Settings API, use the builtin:process-group.detection-flags schema ID.
To be able to use the API you need an access token with Read settings (settings.read) and Write settings (settings.write) scopes. To learn how to obtain it, see Create an access token.
The process group detection requires a restart of the IBM MQ process.
Dynatrace extensions can add technology-specific metrics to the analytics views for ActiveMQ Classic, Apache Kafka, RabbitMQ, and Tibco EMS queues and topics. To get these metrics, you need to configure and activate the extensions in your Dynatrace environment.
Technology-specific metrics provided by Dynatrace extensions consume Davis data units. To learn about Full-Stack Monitoring mode in the context of Davis data units, see Included metrics per host unit.
The ActiveMQ transport configuration of a broker with the IP address 0.0.0.0 is not supported.
This configuration allows the broker to accept incoming messages on all network interfaces, while a broker IP address configured on a specific network interface is required for Dynatrace to establish a connection between the broker and its queues and to show related metrics in the ActiveMQ Classic view.
ActiveMQ Artemis queue and broker metrics are not supported.