Today, a Citrix Virtual Apps and Desktops administrator has no way of proactively being informed if a hypervisor (that is hosting the VDAs) goes down or is rebooted. Therefore the administrator is forced to rely on getting this information from the infrastructure administrator and has to move between Citrix Director (for monitoring CVAD sessions) and the management console of the underlying hypervisor.

Hypervisors have mechanisms to let administrators know when a host may be experiencing some event, condition or state that could affect the machines running on the host. These alerts need to be monitored to ensure the health of the sessions users are connected to. Administrators who are troubleshooting user issues from Director, need not have the host management consoles (Citrix Hypervisor or VMware vSphere Client) open just to see if the hosts are facing any issues. To give administrators a holistic view of the Citrix Virtual Apps and Desktops deployment and all hosts in the deployment at a glance, Hypervisor connections are monitored and the alerts are shown in Director. The administrator can then quickly assess whether the issue the user(s) are reporting is a host related issue or not.

The Hypervisor monitoring is enabled by setting up alerts in Citrix XenCenter or VMware vSphere Client for the hosts that have been configured to be a part of the deployment as defined via Citrix Studio, when creating the site or later.  Therefore, ensure that a hosting connection is created in Citrix Studio. For more information, see Connections and resources. Only these connections are monitored for hypervisor alerts.

The following table describes the various supported hypervisor alerts, the triggering agent, conditions and the configurations needed to obtain the alert.

To learn more about configuring the alerts in the Citrix Hypervisor, see XenCenter Alerts.

To learn more about configuring the alerts in VMware vSphere Client, see Working with Alarms.

A prebuilt policy called Hypervisor Policy is available under Site Policy to monitor the connections. Administrators can modify the name, description and the email notification preference for the alert policy as displayed below. Currently, the policy cannot be disabled or deleted.

Figure 1. Hypervisor Policy

Figure 2. Editing Hypervisor Policy

The thresholds for the alerts need to be set by accessing the hypervisor consoles as mentioned in the above links. Note that specific configurations are not required for the Hypervisor connection unavailable alerts as these alerts are generated when the hypervisor connection is lost or powered down or rebooted. These alerts will continue to be generated for every hour till the connection is restored again. Also, the Host connection or power state alert comes inbuilt with vSphere client and does not need to be configured separately.

Once the alerts are obtained, the notification count is incremented and the alerts are displayed as active alerts. Email is sent to the configured email id in the policy.

Figure 3. Active Alerts and Notification Count

The Alerts are displayed in the Alerts Dashboard page. The Notification Log displays the history of the notification.

Figure 4. All Alerts

Figure 5. Notification History

A new category called Hypervisor Health is introduced to enable the filtering of hypervisor alerts.

The alerts can have the following status:

  • Critical—critical threshold of the hypervisor alarm policy reached or exceeded
  • Warning—warning threshold of the hypervisor alarm policy reached or exceeded
  • Dismissed—alert no longer displayed as an active alert

Alerts triggered by the Hypervisor are fetched and displayed in Director. However, changes in the life cycle/state of the Hypervisor alerts are not reflected in Director. Therefore,

  • Alerts that are healthy or dismissed or disabled in Hypervisor console will continue to appear in Director and have to be dismissed explicitly.
  • Alerts that are dismissed in Director are not dismissed automatically in Hypervisor console.

This feature is available for the latest cloud service and on-prem release  7 1811 or later for both Delivery Controller and Director. If you are using an older version of Director with Sites 7 1811 or later, only the hypervisor alert count is displayed. To view the alerts, Director must be upgraded.