ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

metric values are not being reported by MQMonitor Agent for MQ Manager cluster

book

Article ID: 194551

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management

Issue/Introduction

We have an HA active-active MQ Manager cluster - within the cluster we monitor both servers for MQ and Integration Broker (CA Wily Introscope ver. 10.7.0.197).

On one of the monitored nodes for the MQ Agent we see active metrics, while on the other node there are not the same metrics available - there are much fewer.

Please explain such a situation where the "Current Queue Depth" metric is activated on both nodes:

We can see parameter value. ESB|<Hostname>|WebSphere MQ and Message Broker|WebSphere MQ and Message Broker Agent|Queue Managers|<IP-Address>|AMCD02|Queues|ESB_LOG|Status:Current Queue Depth|)

but only on one of the node, the following metrics are visible:

..Status:Dequeue Count, ..Status:Enqueue Count, ..Status:Queue Time (Long Term Avg.) etc.


What are all possible MQ metrics expected from CA Introscope MQ Agent? Is there any documentation available?


Environment

Release : 10.7

Component : APM Agents

Resolution

We found couple of issues here.

1-

APM release is showing that it is Version: 9.7.0.27.

APM release 9.7 is not supported any more. Please review the drop support information.

https://techdocs.broadcom.com/us/product-content/status/support-life-cycle/indexes/ca-apm-release-and-support-lifecycle-dates.html?r=2

20

APM release is showing that it is Version: 10.7.0.197.

The agent log is not showing any information related to the issue we are facing here.

Based on the MQMonitor.properties, it seems like only one instance of the MQ is being monitored with this agent.

[email protected]<IP_Address>

Please note that default MQMonitor agent (that you download from support download page; https://casupport.broadcom.com/download-center/download-center.html) is not aware of MQ Cluster.

You need to monitor each instance of MQ independently.

Please review the following part in our online guide.

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/implementing-agents/java-agent/java-agent-extensions/ibm-websphere-mq.html

Metrics Reference
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/application-performance-management/10-7/implementing-agents/java-agent/java-agent-extensions/ibm-websphere-mq/metrics-reference.html

Please note that only V7.0, 8.0,9.0 of the WebSphere Message Broker are supported with this agent.

Review compatibility guide.

https://techdocs.broadcom.com/us/product-content/status/compatibility-matrix/application-performance-management-compatibility-guide.html?r=2

If the WebSphere Message Broker is 10, than there is an extension available on APM extension website.

https://github.com/CA-APM/IIB10-Extension

Review the support note at the bottom of the page.
This above extension is supported by APM community and/or
Support URL
https://github.com/CA-APM/IIB10-Extension/issues