DX Application Performance Management

Hi Team,

In CA APM 10.5.2 , can i use 

introscope.enterprisemanager.loadbalancer.enable=false  property to disable default load balancing, if not please provide correct way to do it.

Thanks

Hi Pradeep,

Yes that hidden/undocumented property is still valid in APM 10.5.x.

It should be visible in the IntroscopeEnterpriseManagerSupport.log file:

[INFO] [Manager.Support.Properties] introscope.enterprisemanager.loadbalancer.enable=true

Also in IntroscopeEnterpriseManager.log if DEBUG logging is enabled:

[VERBOSE] [main] [Manager.ClusteredPropertyService] Added introscope.enterprisemanager.loadbalancer.enable=true

It was added back in 9.1 when the Load Balancing was significantly changed - see this related thread: Agent load balancing 

Regards,

Lynn

Thanks Lynn_Williams , for your prompt reply.

If for some reasons, load balancing cannot be disabled, you may also edit loadbalancing.xml to direct certain agent only to connect to a certain collectors.  It could be complex if you have many agent names that don't fall under a certain pattern that could be specified with a regular expression, but it could also be useful to start building on it if load balancing to one day becomes desirable.

Francis

Hi Pradeep,
I have never used the mentioned hidden property before, but I think if you enable this property something strange will happen, something like MOM accepting the agent metrics. This also means MOM won't redirect the agent anymore, but that is not what I would call disabling loadbalancing

This property was originally intended for the CDV mode which is a stripped down version of MOM that does not redirect any agents.

There is no setting to revert the functionality back to pre-9.1 or disable LB.

My recommendation is just don't configure the loadbalancing.xml, is all we have at this point.

If you concern is about possible metric explosion affecting your collectors' metadata, you can configure the MOM to startup with introscope.enterprisemanager.loadbalancing.staywithhistoricalcollector=always this will force the agents to collect to the appropriate collectors, once all of your agents are reconnected, you can change the property value to notoverloaded to restore default load balancing behavior, see https://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1526667.html?intcmp=searchresultclick&resultnum=2

I hope this helps,

Regards,
Sergio