search cancel

How to refresh APM Status Console to get rid of outdated clamp messages


Article ID: 186353


Updated On:


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


The APM status console is showing several clamps for agents exceeding the clamp threshold for maximum number of agent metrics

The agent clamp limit in the apm-events-thresholds-config.xml has been raised on both the Collectors and the MOM and this is reflected in the log as is the fact that the affected agents are now accepting new metrics

1/24/20 11:37:47.020 AM EET [INFO] [scheduler-1] [] Detected hot config change to /opt/COL1/./config/apm-events-thresholds-config.xml
1/24/20 11:37:47.029 AM EET [INFO] [scheduler-1] [Manager.Agent] [Clamp : introscope.enterprisemanager.agent.metrics.limit, Value : 200,000]
1/24/20 11:37:47.029 AM EET [INFO] [scheduler-1] [] [Threshold is changed for Event Type : introscope.enterprisemanager.agent.metrics.limit,[50,000 --> 200,000]
1/24/20 11:37:47.974 AM EET [INFO] [PO:WatchedAgentPO Mailman 12] [Manager.Agent] The Agent JBoss Service Agent is now accepting new metrics (max=200000)
1/24/20 11:37:48.143 AM EET [INFO] [PO:WatchedAgentPO Mailman 9] [Manager.Agent] The Agent JBoss Portal Agent is now accepting new metrics (max=200000)
1/24/20 11:37:49.507 AM EET [INFO] [PO:WatchedAgentPO Mailman 9] [Manager.Agent] The Agent JBoss Service Agent is now accepting new metrics (max=200000)

The problem is that the APM Status Console still shows the old EM limits and clamps caused by those.
How to refresh APM Status Console, so it only shows active clamps and discards old clamps.


The ultimate cause was not identified however it is believed to be related to stale data in the Enterprise Manager cache that was not correctly flushed when the clamps were cleared.


Release : 10.7.0



The clamp information as shown in the APM status console should refresh dynamically as the clamps are cleared. The problem was resolved in this situation by restarting the collectors on which the erroneous clamps were reported.

It is important to note that the problem here was just the incorrect display of clamped agents - the clamps had been cleared by the configuration change and new metrics were being reported.