topic Re: IBM MQ (v2 3.5.10) queue manager status is missing in Extensions

IBM MQ (v2 3.5.10) queue manager status is missing

Yosi_Neuman — Wed, 12 Feb 2025 08:39:50 GMT

Hi guys,

Customer have few queue managers that are in status running as standby

From availability perspective (metric) they appears as not available.

In order to understand if this is a real problem or not we need to see the queue manager status somewhere.

Is that possible some how or we need to open an product idea for that ?

Thanks

Yos

Re: IBM MQ (v2 3.5.10) queue manager status is missing

Babar_Qayyum — Wed, 12 Feb 2025 08:59:21 GMT

Hello @Yosi_Neuman

It appears that we must pursue the product idea, as the status level metrics are exclusively accessible for the channels and queues.

Regards,

Babar

Re: IBM MQ (v2 3.5.10) queue manager status is missing

Yosi_Neuman — Wed, 12 Feb 2025 13:16:50 GMT

Hi @Babar_Qayyum

Thanks for the confirmation.

Found product idea in not planned status, added comment on it....

Will update here with outcomes as soon as will get them

All the best and stay safe

Yos

Re: IBM MQ (v2 3.5.10) queue manager status is missing

Yosi_Neuman — Thu, 20 Feb 2025 14:56:30 GMT

Hi all

Did not get answers on my comment under the product idea in not planned status

Added a new product idea

Yos

Re: IBM MQ (v2 3.5.10) queue manager status is missing

AurelienGravier — Wed, 26 Feb 2025 08:27:07 GMT

Hello @Yosi_Neuman,

I encountered the same issue after the upgrade of the extension :

In my opinion, topology has changed and the metric query on the OOTB dashboard is no longer up to date.

If I check the query related to the dashboard tile, the metric is empty since the upgrade :

The dimension "dt.entity.ibm_i:job" doesn't exist anymore but another one exist "job_name" with data.
But, in my side, it dooesn't match with the number of jobs :

The breaking change on job entities (version 2.2.4), could be the root cause :

The topology has changed on the history of the entity Job (ibm_i:job) :

Re: IBM MQ (v2 3.5.10) queue manager status is missing

Yosi_Neuman — Wed, 26 Feb 2025 14:30:58 GMT

Hi @AurelienGravier,

Thank for your input, in our case we don't see any warning and we did not change the version.

Our issue is with IBM Data Power extension that is not collecting the status of the queue manager to show if its in running or running as standby mode.

Waiting for response from PM on the posted product idea

Thanks again

Yos

Re: IBM MQ (v2 3.5.10) queue manager status is missing

diego_morales — Wed, 26 Feb 2025 16:32:31 GMT

Hi Aurelien,

Your inquiry is about the IBM i extension, not the IBM MQ extension.

IBM i extension creates job entities. The issue you are having is that it's not creating those entities. There is no breaking change, as you noted the metrics exist so the extension is sending the data correctly. It is likely that you ran into a limit issue in that you hit the entity creation limit, or the relationship creation limit.
I recommend contacting support about this so they can confirm this and increase those limits so that job entities are created.

Thanks,

Diego

Re: IBM MQ (v2 3.5.10) queue manager status is missing

AurelienGravier — Wed, 26 Feb 2025 16:48:08 GMT

Hello,

My apologies, I polluted your topic Yosi !
Got it Diego, thx U.

Re: IBM MQ (v2 3.5.10) queue manager status is missing

Kaladhar — Wed, 18 Jun 2025 12:01:39 GMT

Hi @Yosi_Neuman

I hope you tried this already but I just want to update on the 3DNS or Load balancer.

When you say the Queue manager status is 'Running as Standby' it means the the QMGR is 'RUNNING' in the active node.

If you can set up a 3DNS record/Load Balancer for the both active and nodes, then the Dynatrace request to pull QMGR data will only go to the current active node and displays the status as 'RUNNING' which avoids the the 'Not Available Status'

Thanks.

Re: IBM MQ (v2 3.5.10) queue manager status is missing

Yosi_Neuman — Mon, 23 Jun 2025 05:46:46 GMT

Hi @Kaladhar

Not a big expert in IBM MQ hence can you please explain how to set the 3DNS record/Load Balancer or point to the IBM MQ documentation on how to do that?

Thanks

Yos