Also the DC RUM 12.4.5 highlights the new MQ decode which now is able to correlate messages between multiple queue managers and report the end to end transactions. Please see https://community.dynatrace.com/community/display/PROD/DC+RUM+12.4+Release+Notes and look for "Superior IBM MQ transaction flow analysis" in 12.4.5 section:
True IBM WebSphere MQ transaction performance analysis requires automated correlation of multiple network conversations between distributed hosts while supporting multiple protocol variations and versions. The new DC RUM decode for WebSphere MQ measures true transaction flow, enabling you to:
Hmmm, must be missing something as I originally thought this was only for HS AMDs. In my 12.4.12 classic amds (or MQ software services) I don't see any settings for controlling the generation of ADS data for MQ (which this looks to be)
I have a follow up question on this. I am using 12.4.7 with a HS AMD attempting to monitor 2 queues on a single queue manager that i am trying to correlate together with no luck so far. Upon inspecting a packet capture i have confirmed that MSG ID is being used on the reply of the Put and Get. what i am specifically trying to measure is the time from the put of a message on a request queue, to the time of the get of that message off of the corresponding reply queue. Im not sure if there is something i am missing in my configuration or the traffic that is causing this not to correlate?
We're wondering the same thing... but currently using Dynatrace OneAgent (not APM based), running v1.135
We have two hosts running IBM Message Queue and have installed agents on both. We can see that Dynatrace has picked up IBM MQ on each host but we don't seem to be getting any detailed information. There's no indication as to what queues are installed / running or any further metrics for that matter.
Not sure if there's anything else we need to enable as there are no process restarts pending.
We've raised a ticket for this already but thought I'd put it out to the community to see if anyone else has had any experience in this scenario.
OneAgent doesn't support deep MQ monitoring yet. Some unofficial works exist, see https://github.com/Dynatrace-Reinhard-Pilz/OneAgent-IBM-MQ-Channel-Plugin (not officially supported). It's an open topic for the future, so a suggestion/product idea on the Dynatrace forum makes perfect sense - see this: https://answers.dynatrace.com/spaces/483/dynatrace-product-ideas/idea/187619/rfe-ibm-mq-support.html?_ga=2.105587523.1383987297.1518611741-1287679700.1488289333
In the mean time, MQ monitoring can be addressed by DC RUM probe (AMD) deployed to sniff in front of the servers (that's what this thread references). Queue and manager names, user names, calling programs (if specified) will be reported, together with transaction times. MQ traffic analysis can also reach deep into the MQ payload to extract relevant transaction names. @Andrew L. please let me know if you are interested in a further discussion/review of what can be done with the agentless MQ monitoring.
I have raised that in the above post link...
Ps) It may be worth pointing out that in the release notes for a recent OneAgent update, it references the IBM MQ monitoring capability. The details of exactly what this offered weren't specified, but it was certainly referenced.