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. To establish this communication, the Endpoint agent requires the details of the eG remote agent it should transmit metrics to. To feed this information to the Endpoint agent, you can do one of the following:

    • The recommended approach is to configure the Endpoint agent with the details of the eG remote agent it should communicate with;

    • Alternatively, you can configure the Endpoint agent with the details of the eG manager. In this case, the Endpoint agent will connect with the configured manager and download the details of the eG remote agent that is responsible for monitoring the target IGEL Endpoint.

    Once the Endpoint agent determines the remote agent it should communicate with, it starts collecting the 'inside view' metrics for the target IGEL Endpoint and caches the metrics so collected. The Endpoint agent then pushes the cached 'inside view' metrics to the remote agent via TCP port 60010 by default. 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.

    eG Remote Agent Communication

    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.