Missing agent nodes even when clonedAgent=true

book

Article ID: 143177

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

 Agent instances missing from the console even when clonedAgent=true. 

Sometimes agents connect to collectors with the exact same name when they should have different names because the clonedAgent feature is true. This happens when the MOM and collectors are starting up or restarting.  In this case, we will see agents that have the exact same name on different collectors and the MOM will not allow them both to be mounted. 

 

 

 

 

 

Cause

Per engineering:

"Agents connecting to the collectors with the exact same name when they should have different names because the clonedAgent feature is true"

It is a known issue/limitation that the agent with same name connecting to different collectors will still keep the same name, no matter cloneAgent is true or not.

There is an ER opened to provide unique agent name across cluster, long time ago. no ETA yet. 

Environment

Release : 10.7.0

Component : APM Agents

Resolution

The current workaround is to configure loadbalancing.xml to make sure agents with same name go to same Collector so that unique name can be assigned for each.