How to Monitor VDI-in-a-Box Using eG Enterprise?
eG VDI-in-a-Box Monitor model monitors the VDI-in-a-Box in an agentless manner. For this purpose, you require a single eG agent to be deployed on a remote Windows/Linux host in your environment. This remote agent should be configured to:
- Connect to the vdimanager via SSH and pull out metrics related to the overall health and availability of the vdimanager and the usage of the virtual desktops it manages;
- Connect to the physical server on which the vdimanager operates, and report on the health and resource usage of the host, the hypervisor, and the virtual desktops using a patented ‘In-N-Out’ monitoring algorithm.
To enable the eG agent to pullout metrics, a set of pre-requisites should be fulfilled. These requirements are discussed in the section below.
Pre-requisites for monitoring VDI-in-a-Box?
To enable the eG remote agent to pull out all these performance statistics, you first need to make sure that the following pre-requisites are in place:
For monitoring the vdimanager:
- The eG agent should be able to connect to the vdimanager via SSH and pull out the metrics. For this purpose, the default SSH port, 22, should be opened on the vdimanager. If your environment has been configured with a different SSH port, then make sure that that port is open.
- The eG agent should be able to login to the vdimanager appliance for monitoring and metrics collection. To enable this, you need to configure all tests that the eG agent executes on the vdimanager with the credentials of a user with login rights. By default, the appliance supports a root user named root and a user named kvm. If you prefer not to expose the credentials of the root user, then you can configure the tests with the credentials of the other user, kvm, for this purpose. By default, the user root takes the password root, and the user kvm takes the password kaviza123.
For ‘In-N-Out’ monitoring of the VMware vSphere server and its VMs:
Make sure that the pre-requisites detailed in Section 2.1 of the Monitoring VMware Infrastructures document are fulfilled.
For ‘In-N-Out’ monitoring of the Citrix XenServer and its VMs:
Make sure that the pre-requisites pertaining to ‘agentless’ monitoring of XenServers (detailed in Section 1.3.2 of the Monitoring XenServers document) are fulfilled.
For ‘In-N-Out’ monitoring of the Microsoft Hyper-V and its VMs:
Make sure that the pre-requisites pertaining to ‘agentless’ monitoring of the Hyper-V server (detailed in Section 1.3 of the Monitoring Microsoft Hyper-V document) are fulfilled.