[APM] Visibilty of agents, which attach / detach often
search cancel

[APM] Visibilty of agents, which attach / detach often


Article ID: 259887


Updated On:


CA Application Performance Management (APM / Wily / Introscope)


Followup for 33309438 [APM] No Post Office Specified Exception

The customer has the following question in addition regarding this error:

"Can we somehow trigger this frequent attach/detach of agents with any metrics in APM?"


Release :


Currently there is no way to simulate a attach/detach of an agent with respect to a specific metric or any metrics.  The only way to do this is to stop and start the Agent.

However, if you want to block the Agent from connecting, on the MOM you would use load balancing.  The file is located in <MOM home>/config/loadbalancing.xml.  Here you can elect to force a specific Agent (or more than 1) to go to a specific Collector or not be allowed to connect to the cluster at all.

See links below.  Also the loadbalancing.xml file has examples inside of it as well.




Also for your logging question, there is no other method than setting log4j.logger.Manager to DEBUG for any agent connection/disconnection.

On the Agent side, same thing.  Only setting log4j.logger.IntroscopeAgent to DEBUG for any agent connection/disconnection.