How Does eG Enterprise Monitor IGEL Endpoints?
eG Enterprise monitors IGEL endpoints in an agentless manner.
Pre-Requisites for monitoring IGEL Endpoints
For internal monitoring of the IGEL Endpoints, an extremely light-weight, Endpoint Agent has to be installed on each of the IGEL Endpoints.
By default, an eG remote agent on a remote Windows/Linux host is used for monitoring the IGEL endpoints. However, the remote agent does not initiate any communication with the Endpoint Agent on the individual IGEL Endpoint. This is because, this remote agent has no knowledge of the hypervisor on which the IGEL Endpoints are operating. Therefore, it can neither discover the IP address/host name of the IGEL Endpoints, nor can it communicate with them to collect the 'inside view' metrics.
This is why, the Endpoint Agent installed on the IGEL Endpoint has been specifically engineered to initiate all communication. The Endpoint Agent on an IGEL Endpoint first communicates with the eG manager to know which remote agent has been assigned to that IGEL Endpoint. Then, the Endpoint Agent pushes the cached 'inside view' metrics to that remote agent via TCP. To enable this communication, a TCP port has to be opened on the eG remote agent. If the remote agent is behind a firewall, then make sure that the firewall is configured to allow one-way communication from the Endpoint Agent to the remote agent. Upon receipt of the 'inside view' metrics, the remote agent sends the metrics to the eG manager.
Figure 1 : The Endpoint Agent - eG Remote Agent communication when monitoring IGEL Endpoints
- When monitoring IGEL Endpoints, the remote agent needs to be in the same subnet as that of the Endpoint Agent or accessible on the local network of the Endpoint Agent.
- Ensure that the Endpoint Agent communicates with the IP address of the remote agent directly and that the communication is not via a NAT or port forward.