topic Re: IBM MQ Monitoring issue in Extensions

IBM MQ Monitoring issue

kiranraju — Tue, 01 Apr 2025 08:48:32 GMT

We are observing that Dynatrace is adding dtdTraceTagInfo into messages sent by One of the applications to the downstream system which is causing messages to fail on the downstream side as they are not able to parse the message due to the presence of these additional named properties in MQ message.

We would like to know the are there any possibilities for disabling the "dtdTraceTagInfo" at the Queue or Host level in Dynatrace UI.

Re: IBM MQ Monitoring issue

ChadTurner — Tue, 24 Jan 2023 12:35:05 GMT

@kiranraju were you able to get a work around to disable that dtdtaginfo in the messages? if not you might need a support ticket. Once you get the solution could you please share it with the community?

Re: IBM MQ Monitoring issue

JamesKitson — Wed, 25 Jan 2023 21:12:34 GMT

FYI this would be something done by the OneAgent not the IBM MQ extension. I'll move this to a more appropriate forum.

Re: IBM MQ Monitoring issue

Babar_Qayyum — Thu, 26 Jan 2023 06:19:59 GMT

Hello @kiranraju

If I am not mistaken you are talking about the messaging service but not the extension. Am I correct? It is a custom message property so there should be a way to remove this but I am not sure what the consequences will be.

https://www.dynatrace.com/support/help/how-to-use-dynatrace/queues/queue-concepts

Regards,

Babar

Re: IBM MQ Monitoring issue

AntonioSousa — Thu, 17 Aug 2023 13:57:03 GMT

In one case I have dealt with, involving in this case JMS, we had to disable JMS at the PG level. The process still had visibility in the remaining services, but JMS visibility was lost.

Re: IBM MQ Monitoring issue

AndrasKovacs — Thu, 17 Aug 2023 12:17:15 GMT

Hi @kiranraju,

we are also facing the same issue. What was the solution in your case?

Thanks in advance!

Re: IBM MQ Monitoring issue

kiranraju — Thu, 17 Aug 2023 17:56:34 GMT

Hi @AndrasKovacs ,

We have tried some possibilities which are suggested by the support team, but those didn't help.

So, the development team has made the changes in the code level to ignore the named properties. Because of that, we are not getting the dtdTraceTagInfo values (removed the MQ series sensor), and messages are succeeded to the downstream applications.

Re: IBM MQ Monitoring issue

AndrasKovacs — Fri, 18 Aug 2023 05:56:06 GMT

Thanks @kiranraju. And does it have any negative effect on the monitoring? Do you miss out on anything? I guess you don't see the custom messages, right?

Re: IBM MQ Monitoring issue

kiranraju — Thu, 02 Nov 2023 13:39:36 GMT

@AndrasKovacs - We haven't seen any negative impact and nothing missed.

Re: IBM MQ Monitoring issue

36Krazyfists — Thu, 09 Oct 2025 18:52:49 GMT

Old post I know, but I imagine the issues would be at the Trace level because I believe this value is used to hold contextual trace/span id information that is used for connecting distributed traces.

Re: IBM MQ Monitoring issue

Julius_Loman — Fri, 10 Oct 2025 06:53:41 GMT

@36Krazyfists not really - AFAIK traces across MQ are stiched on the Dynatrace cluster based on queue names.