Agents Administration - Tests
 

Configuration of WVDUptimeTest

In most VDI environments, it is essential to monitor the uptime of virtual desktops hosting critical applications in the infrastructure. By tracking the uptime of each of the virtual desktops, administrators can determine what percentage of time a virtual desktop has been up. Comparing this value with service level targets, administrators can determine the most trouble-prone areas of the VDI infrastructure.

In some environments, administrators may schedule periodic reboots of their virtual desktops. By knowing that a specific desktop has been up for an unusually long time, an administrator may come to know that the scheduled reboot task is not working on a desktop.

This test included in the eG agent monitors the uptime of a chosen Session Host / Azure virtual desktop.

The default parameters associated with this test are as follows:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, the IP address of the host for which the test is to be configured has to be specified.

  • Specify the port at which the specified HOST listens to in the PORT text box. By default, this is NULL.

  • By default, the REPORT MANAGER TIME flag is set to Yes, indicating that, by default, the detailed diagnosis of this test, if enabled, will report the shutdown and reboot times of the virtual desktop in the manager's time zone. If this flag is set to No, then the shutdown and reboot times are shown in the time zone of the system where the agent is running (i.e., the Session Host being monitored).

  • Typically, the first time this test executes on a Windows host, it creates a sysuptime_<Nameofmonitoredcomponent>.log in the <EG_AGENT_INSTALL_DIR>\agent\logs directory. This log file keeps track of the system reboots - each time a reboot occurs, this log file is updated with the corresponding details. During subsequent executions of this test, the eG agent on the Windows host reads this log file and reports the uptime and reboot-related metrics of the target. In case of a physical Windows host, this log file ‘persists’ in the said location, regardless of how often the system is rebooted. However, in case the target Windows system has been ‘provisioned’ by a Provisioning server, this log file is recreated in the <EG_AGENT_INSTALL_DIR>\agent\logs directory every time a reboot/refresh occurs. In the absence of a ‘persistent’ log file, the test will not be able to track reboots and report uptime accurately. To avoid this, when monitoring a provisioned Windows system/server, you have the option to instruct the test to create the sysuptime_<Nameofmonitoredcomponent>.log file in an alternate location that is ‘persistent’ - i.e., in a directory that will remain regardless of a restart. Specify the full path to this persistent location in the LOG LOCATION text box. For instance, your LOG LOCATION can be, D:\eGLogs. In this case, when the test executes, the sysuptime_<Nameofmonitoredcomponent>.log file will be created in the D:\eGLogs\eGagent\logs folder. By default, the Log Location parameter is set to none.

  • The DD FREQUENCY parameter refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY .

  • To make diagnosis more efficient and accurate, the eG suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability.

    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.