cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

IBM MQ New Extension

Esam_Eid
Pro

Dears,

We started using the new IBM MQ extension for MQ monitoring, we have noticed that the Cluster Senders which are automatically created are not discovered by the extension, but only the manually created Cluster senders are discovered. 

Is this a limitation? Or is there any workaround to fix this?

Thank you! 

2 REPLIES 2

diego_morales
Dynatrace Advisor
Dynatrace Advisor

Hi there,

It is a limitation as auto-defined channels are never returned by IBM MQ during searches, so we are limited by IBM MQ's API.

Thanks,

Diego

Hi @diego_morales,

I have shared your response with our MQ expert and below is his feedback.  if you want we can discuss it offline. Thanks!

 

In my PCF program I can return the details that I need – my monitoring program that I wrote can collect these details for me.

If you do dis chs(*) it shows all running channels. This can be converted to a PCF command.
If you do dis clusqmgr(*) this will show the cluster queue manager details (can use a PCF command), including channel details. Note that this may miss some values if the cluster connections weren’t established both ways (some cluster connections may be established only one way – e.g. if the connection is only send-and-forget messages).

The most important consideration is with MQ clustering is that the cluster channels are mostly auto-generated. The only manual generated ones should be to the cluster full repos queue managers. This adds no value. We need the cluster sender channels to the app queue managers (dis chs(*)) as that contains critical details like network time, and other metrics that can only be obtained on the sending end of the channels.

Featured Posts