How Does eG Enterprise Monitor Amazon Cloud Desktop Group?
eG Enterprise monitors the Amazon Cloud Desktop Group in an agentless manner.
Pre-Requisites for monitoring Amazon Cloud Desktop Group
For internal monitoring of the individual cloud-based virtual desktop, a light-weight eG VM Agent has to be installed on each of the virtual desktops.
An eG remote agent on a remote Windows/Linux host is used for monitoring. The remote agent does not initiate any communication with the eG VM Agent on the individual virtual desktop. This is because, this remote agent has no knowledge of the Amazon Cloud Desktop Group on which the virtual desktops are operating. Therefore, it can neither discover the IP address/host name of the Amazon Cloud Desktop Group, nor can it communicate with them to collect the 'inside view' metrics.
This is why, the eG VM Agent on a virtual desktop has been specifically engineered to initiate all communication. The eG VM Agent on a virtual desktop first communicates with the eG manager to know which remote agent has been assigned to that desktop. Then, the eG VM 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 eG VM agent to the remote agent. Upon receipt of the 'inside view' metrics, the remote agent sends the metrics to the eG manager.
Figure 1 : How does the eG VM Agent communicate with the eG Remote Agent
When monitoring Amazon Cloud Desktop Group, the remote agent needs to be in the same subnet as that of the eG VM Agent or accessible on the local network of the eG VM Agent.
Ensure that the eG VM Agent communicates with the IP address of the remote agent directly and that the communication is not via a NAT or port forward.