search cancel

APM console showing agent Metric Clamp

book

Article ID: 201644

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

Currently the APM console is showing alarms of metric clamp. All collectors showing alarms of metric clamp. We want to consult about the recommendations that we should make to correct these alarms. Most of these alarms are for .NET Agent.

Environment

Release : 10.7.0

Component : APM Agents

Resolution

Most of the agents are showing the following:

9/22/20 09:35:47 AM GMT-05 [WARN] [IntroscopeAgent.Agent] Absolute metric clamp of 5000 reached, no more metrics can be created. Instrumentation on this application should be reduced.
9/22/20 09:35:47 AM GMT-05 [WARN] [IntroscopeAgent.Agent] Note: if no more metrics can be created when the agent starts up, there may be exceptions in the startup process. Increasing the clamp value may solve these exceptions.
9/22/20 09:35:47 AM GMT-05 [INFO] [IntroscopeAgent.Agent] CLAMP EVENT: Agent was not clamped before; New metric has been created and agent has hit the metric clamp.

This means that agent is already reporting 5000 metrics and agent hit the metric clamp. Thus you see these alarm messages in the APM console.

Option 1:
If you increase the clamp you need to make sure that APM cluster/Standalone EM does not have an high impact.

In the IntroscopeAgent.profile, you can adjust the following.

introscope.agent.metricClamp=5000

to

introscope.agent.metricClamp=8000

OR

introscope.agent.metricClamp=10000

You can test on 1 agent and see the results.

Option 2:
The better option is to reducer the .NET agent instrumentations.

Adjust and reduce the perfmon agent configuration so it only gather the relevant perform counters. Adjust the value for follow property accordingly.

introscope.agent.perfmon.metric.filterPattern

You can also disable the following.

1) Disable Socket instrumentation in the toggles-typical or toggles-full.pbd by commenting the below line:
TurnOn: SocketTracing

2) Disable WCF/SOAP header insertion in the webservices.pbd by commenting the below lines:
TurnOn: WCFRuntimeTracing
TurnOn: WebServicesCorrelationTracing
TurnOn: WCFServerFaultTracing
TurnOn: WCFClientFaultTracing
TurnOn: WCFServerTracing
TurnOn: WCFClientTracing

3) Reduce SQL instrumentation:
introscope.agent.sqlagent.sql.turnoffmetrics=true
introscope.agent.sqlagent.sql.artonly=true
introscope.agent.sqlagent.sql.turnofftrace=true

introscope.agent.sockets.reportRateMetrics=false

introscope.agent.transactiontracer.tailfilterPropagate.enable=false

Stop the IIS and delete all agent logs, then start the IIS.

Attachments