search cancel

MSMQ Queue metrics are not reported by PerfmonCollectorAgent even though we have defined the filter to include them

book

Article ID: 216491

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

We have added MSMQ counters reported by perfmon in the server to the PerfmonCollectorAgent filter property in the Introscope agent profile 
 
introscope.agent.perfmon.metric.filterPattern=|Processor|*|*,|.NET Data Provider*|*|*,|.NET CLR*|{osprocessname}|*,|.NET CLR Data|*|*,|Process|{osprocessname}|*,|ASP.NET*|*,|MSMQ Queue|*|*
 
Agent service has been restarted.
 
Still MSMQ metrics are not populated in CA APM Metric browser.

Environment

Release : 10.7.0

Component : APM Agents

Cause

The agent log showed the metric limit is being reached before it browses the MSMQ metrics
 
5/24/21 02:42:40 PM GMT+02 [VERBOSE] [IntroscopeAgent.PerfMonService] Metric limit of 1000 has been reached
...
5/24/21 02:42:43 PM GMT+02 [DEBUG] [IntroscopeAgent.PerfMonService] Browsing Category counters with instances MSMQ Queue

Resolution

 
There are two options available here (customer chose #2)
 
1 - increase the metric limit by uncommenting and modifying the following property value in the agent profile
 
#introscope.agent.perfmon.metric.limit=1000
 
care should be taken though as querying the perfmon counters can affect system performance if excessive
 
2 - filter the metrics collected - do you need / are you interested in all the counters that re reported by default - would it make more sense to cut back on what is currently reported from the existing property value
 
introscope.agent.perfmon.metric.filterPattern=|Processor|*|*,|.NET Data Provider*|*|*,|.NET CLR*|{osprocessname}|*,|.NET CLR Data|*|*,|Process|{osprocessname}|*,|ASP.NET*|*,|MSMQ Queue|*|*