Directly connect an agent to a collector

[Carlos Hugo Martin Carranza Olivera]

Hello everyone.
The client requests that we monitor his Kubernetes that is in the cloud, for this the Kubernetes Monitor has been used which communicates to a public IP that redirects it to a collector. The problem is that when the agent is connected to the collector through the public IP, the collector sends the list of the collectors that are inside the network and it is no longer possible for the agent to send the metrics since it can not be communicated to none of the collectors on this list. It should be noted that the hostnames of the collectors are present in the list, but we can not modify the hosts files of the servers where the Kubernetes is implemented since the guarantee would be lost.

[Hallett German]

Can someone offer Carlos some suggestions on next steps? Thanks

[Lynn Williams]

Hi Carlos,

It sounds like you need to edit your loadbalancing.xml file on the MOM to limit the Kubernetes agent to just connect to the required Collector and exclude the others. That load balancing information will then be propagated to all Collectors in the cluster. If you also cannot connect the agent direct to the MOM then connecting it to the Collector in the agent profile should I think still work with that load balancing configuration. 

Some relevant wiki pages:

How Agent Connection Information Propagates Across Introscope - CA Application Performance Management - 10.7 - CA Techno… 

Configure loadbalancing.xml for Allowed and Disallowed Agents by Enterprise Manager - CA Application Performance Managem… 

Hope that helps.

Regards,

Lynn