Anyone with Experience on IMB Message Broker monitoring?!

[Anon Anon]

hi Everyone!

In a very critical and strategical project we're trying to monitor IBM Message Broker usage but there are problems in getting statistics from execution groups.
What's strange is that in a Q&A Environment we can get every statistics, but not in the Production environment.

Anyone here with some good experience in this MQ PowerPack?

regards,
Marco Scala

[Anon Anon]

I have used this PowerPack for many years. What doesn't work?

[Legacy User]

Was this ever answered. I have this problem often. Many times the MQ admins will tell me they have enabled stats and most times I see them and some times I don't, as if they were never enabled....

[Haruhiko Davis]

We have support for IIB through our MQ Monitor Agent.

We also have support for MQ Topic via a supported FieldPack.

[Legacy User]

I am using the MQMonitor agent to connect to the IIB9 broker. I can see stats on most flows so I know the agent is configured properly but for some reason on a select few I can never see them. I actually opened a ticket with support this morning because we need these metrics. There is just no resolution for this yet.

[Lynn Williams]

Hi Jordan,

I see my colleague jAmEs_shIn is working the case with you and you have upgraded to 10.x with no benefit.

Have you already looked at this MQ troubleshooting section of the 10.2 wiki? There are some "flow statistics" related tips especially the first one on "JMS Broker Queue manager does not have suitable user permission" relating to MQMonitor user privileges:

WebSphere MQ Troubleshooting - CA Application Performance Management - 10.2 - CA Technologies Documentation

 

Hope it is of some help

 

Lynn

[Legacy User]

Lynn, Thanks for the response.

 

I don't see any of the errors from the that wiki page in my logs. Also under the same broker most flows display stats just fine and it seems to be just one or two flows that wont display stats.

 

Below are the only errors I see related to stats in agent logs. These appear after the connection can not be established to the secondary broker though so they could be only related to that...

 

3/13/16 12:50:53 AM EST [ERROR] [com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.MBTreeMsgflowStatistics] Interrupted..Closing JMS Objects.

3/13/16 12:50:53 AM EST [ERROR] [com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.MBTreeMsgflowStatistics] JMSCMQ0002: The method 'MQCTL' failed.

3/13/16 12:50:53 AM EST [ERROR] [com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.MBTreeMsgflowStatistics] Error occurred  in JMS operation.Closing JMS objects...

3/13/16 12:50:53 AM EST [ERROR] [com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.MBTreeMsgflowStatistics] MBTreeMsgflowStatistics thread ended.

and

3/29/16 09:18:19 PM EDT [ERROR] [com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.ExecutionGroupTracer] Statistics for all Execution groups are missing. MB Agent probably lost connection.

 

Thanks,

Jordan

[Legacy User]

We found a solution to this. I will leave it here in case any one else has this issue.

 

In our case the mq admins must use the MQ Explorer gui and not the command line to enable statistics. Using a command like "mqsichangeflowstats QPX1BRK -s -e CDHSRVR1 -f CDH_ENT_CustomerSearch_V3 -c active" had no effect to APM while right clicking on the flow and clicking enable statistics from MQ Explorer gui worked perfectly. Our MQ Admins are going to check with IBM to see whether there is a difference in using the gui vs cmd line...