To make life a little easier for everyone: when a service puts an item on a queue JMS/MQ and the next service picks it up. There is no way for dynatrace to stitch this together?
Dynatrace does not inject MQ items, but is does JMS?
If a service puts an item on a queue and later retrieves it (within the same thread) from the same queue. Dynatrace will register one queue with in and outgoing traffic?
I have noticed many discussions about this. Who can resolve this once and for all?
Solved! Go to Solution.
what I found so far:
MQ does not work, adding a tag would disrupt mainframe MQ.
JMS line queue’s purepath’s should work out of the box. There should be a reserved space in the protocol to place the DT tag?
JMS is traced using an injected header with a Dynatrace tag in it, just like http.
MQ is traced by comparing the combination of message id, queue name and queue manager name. So there is no injection that would break the mainframe integration. If the tracing does not work maybe you are using something like cluster queues, alias queues or remote queues. In this case the IBM MQ extension and this blog post would be helpful: https://www.dynatrace.com/news/blog/breaking-down-barriers-ibm-mq-tracing-across-queue-managers-and-...
Thank you for the reply!
As an extra, from the documentation: As long as each message is sent and received within the same queue, you get an end-to-end view of each message trace