Issue/Introduction:
Symptoms:
Denied agents appear in Workstation. According to the agent log, the agent is connected but it is in disallowed mode.
Environment:
This behavior can occur on all APM platforms.
Cause:
The following items are possible reasons for this occurrence:
- Due to configuration in loadbalancing.xml preventing an agent from connecting to any Collector.
- Due to the following configuration combinations:
The introscope.apm.agentcontrol.agent.allowed property (in the Collector IntroscopeEnterpriseManager.properties) is set to true and loadbalancing.xml (config file on MOM server) disallows the agent.
The introscope.apm.agentcontrol.agent.allowed property is set to false and the loadbalancing.xml file does not explicitly allow the agent.
Either of these clamp values are reached or exceeded:
introscope.enterprisemanager.agent.disallowed.connection.limit (in the Collector IntroscopeEnterpriseManager.properties)
introscope.enterprisemanager.agent.connection.limit (in MOM apm-events-thresholds.config.xml)
Resolution:
Review loadbalancing.xml configuration and syntax. If needed revert back to a default Out Of The Box file.
Make sure the IntroscopeEnterpriseManager.properties and apm-events-thresholds.config.xml have the appropriate values for clamps in your environment.
Environment:
Release: CEMUGD00200-10.1-Introscope to CA Application-Performance Management-Upgrade Mai
Component: