The following alerts are triggered when any of the monitoring resources in the Horizon Management Pack adapter display an unexpected behavior.
Alert |
Description |
---|---|
Horizon VDI Application Session is experiencing high CPU usage |
Triggered when the Horizon VDI Application Session is experiencing high CPU usage. |
Horizon RDS Application Session is experiencing high CPU usage |
Triggered when the Horizon RDS Application Session is experiencing high CPU usage. |
Horizon VDI Application Session is experiencing high number of received packets dropped |
Triggered when the Horizon VDI Application Session is experiencing high number of received packets dropped. |
Horizon RDS Application Session is experiencing high number of received packets dropped |
Triggered when the Horizon RDS Application Session is experiencing high number of received packets dropped. |
Horizon VDI Application Session is experiencing high number of transmitted packets dropped |
Triggered when the Horizon VDI Application Session is experiencing high number of transmitted packets dropped. |
Horizon RDS Application Session is experiencing high number of transmitted packets dropped |
Triggered when the Horizon RDS Application Session is experiencing high number of transmitted packets dropped. |
Horizon VDI Application Session is experiencing high Protocol latency |
Triggered when the Horizon VDI Application Session is experiencing high Protocol latency. |
Horizon RDS Application Session is experiencing high Protocol latency |
Triggered when the Horizon RDS Application Session is experiencing high Protocol latency. |
Horizon RDS Desktop Session is experiencing high CPU usage |
Triggered when the Horizon RDS Desktop Session is experiencing high CPU usage. |
Horizon RDS Desktop Session is experiencing high number of received packets dropped |
Triggered when the Horizon RDS Desktop Session is experiencing high number of received packets dropped. |
Horizon RDS Desktop Session is experiencing high number of transmitted packets dropped |
Triggered when the Horizon RDS Desktop Session is experiencing high number of transmitted packets dropped. |
Horizon RDS Desktop Session is experiencing high Protocol latency |
Triggered when the Horizon RDS Desktop Session is experiencing high Protocol latency. |
Horizon VDI Session is experiencing high CPU usage |
Triggered when the Horizon VDI Session is experiencing high CPU usage. |
Horizon VDI Session is experiencing high number of received packets dropped |
Triggered when the Horizon VDI Session is experiencing high number of received packets dropped. |
Horizon VDI Session is experiencing high number of transmitted packets dropped |
Triggered when the Horizon VDI Session is experiencing high number of transmitted packets dropped. |
Horizon VDI Session is experiencing high protocol latency |
Triggered when the Horizon VDI Session is experiencing high protocol latency. |
Horizon Session is experiencing high CPU ready time |
Triggered when the Horizon Session is experiencing high CPU ready time. |
Horizon Session is experiencing high disk latency |
Triggered when the Horizon Session is experiencing high disk latency. |
Horizon Session available memory is very low |
Triggered when the Horizon Session available memory is very low. |
Desktop provisioning error |
Triggered when the Desktop provisioning error occurs. |
VDI agent status not available |
Triggered when the VDI agent status not available. |
VDI Desktop Pool has no available desktops |
Triggered when the VDI Desktop Pool has no available desktops. |
VDI Pool provisioning status disabled |
Triggered when the VDI Pool provisioning status is disabled. |
VDI virtual machine available storage below 10% |
Triggered when the VDI virtual machine available storage is below 10 percent. |
VDI virtual machine memory consumption above 90% |
Triggered when the VDI virtual machine memory consumption is above 90 percent. |
VDI virtual machine CPU consumption above 90% |
Triggered when the VDI virtual machine CPU consumption is above 90 percent. |
RDSH Desktop Pool provisioning status disabled |
Triggered when the RDSH Desktop Pool provisioning status is disabled. |
RDSH hosted desktop memory consumption above 90% |
Triggered when the RDSH hosted desktop memory consumption is above 90 percent |
RDSH hosted desktop session CPU consumption above 90% |
Triggered when the RDSH hosted desktop session CPU consumption is above 90 percent |
RDSH Host CPU% disparity exceeds 30% of peer utilization |
Triggered when the RDSH Host CPU% disparity exceeds 30 percent of peer utilization. |
RDSH host memory configuration exceed best practices |
Triggered when the RDSH host memory configuration exceeds best practices. |
RDSH host memory configuration is below best practices |
Triggered when the RDSH host memory configuration is below best practices. |
RDSH host vCPU configuration exceed best practices |
Triggered when the RDSH host vCPU configuration exceeds best practices. |
RDSH host vCPU configuration is below best practices |
Triggered when the RDSH host vCPU configuration is below best practices. |
RDSH hosts in error states |
Triggered when the RDSH host is in an error state. |
RDSH hosted maximum session per host exceeds best practices |
Triggered when the RDSH hosted maximum session per host exceeds best practices. |
RDSH virtual machine available storage below 10% |
Triggered when the RDSH virtual machine available storage is below 10 percent. |
Active session per Connection server exceeds best practices |
Triggered when the Active session per Connection server exceeds best practices. |
Connection server certificate status is invalid |
Triggered when the Connection server certificate status is invalid. |
Connection server configuration not as per best practices |
Triggered when the Connection server configuration is not as per the best practices. |
Connection server service is not running |
Triggered when the Connection server service is not running. |
No valid license for Horizon view |
Triggered when there is no valid license for Horizon view. |
Active session per POD exceeds best practices |
Triggered when the active session per POD exceeds best practices. |
Enabled connection server count exceeds best practices |
Triggered when the Enabled connection server count exceeds best practices. |
Max RDSH server per farm exceeds best practices |
Triggered when the Max RDSH server per farm exceeds best practices. |
Number of virtual machines per pool exceeds best practices |
Triggered when the Number of virtual machines per pool exceeds best practices. |
CPA replication error across PODs |
Triggered when the CPA replication error across PODs. |
CPA site down status |
Triggered when the CPA shows the site down status. |
Global entitlement pool down status |
Triggered when the Global entitlement pool shows the down status |
Maximum number of active sessions in a CPA pod federation exceeds best practices |
Triggered when the Maximum number of active sessions in a CPA pod federation exceeds best practices. |
Maximum number of PODs in a CPA pod federation exceeds best practices |
Triggered when the Maximum number of PODs in a CPA pod federation exceeds best practices. |
Maximum number of sites in a CPA pod federation |
Triggered when the Maximum number of sites in a CPA pod federation. |
POD failed to communicate with target POD |
Triggered when the POD failed to communicate with target POD. |
Data Collection Failed on Horizon Connection Server |
Triggered when the data collection fails on the Horizon connection server.
Note:
Verify the network connectivity of the vRealize Operations Collector and the Horizon Connection server. Verify the health of the Horizon Connection Manger. Update the certificates of the Horizon Connection Server in vRealize Operations cloud instance if the log reports the failure is due to certificate validation. |
Either the Horizon Pod or the managed vCenter Server is not monitored by the vRealize Operations Cloud Instance |
Triggered when the managed vCenter server is not available.
Note:
The vCenter servers hosting the Horizon Pod environment must be monitored by the same vRealize Operations Cloud instance. |
Notification Event Alert on GET API Failure on object Collection |
Triggered when the GET API fails to collect object data.
|
Notification Event Alert on Pod for collection failures |
Triggered when Pod fails to collect data.
|
Notification Event Alert on relationship Failure |
Triggered when relationship fails between objects.
Note:
The vCenter servers hosting the Horizon Pod environment must be monitored by the same vRealize Operations Cloud instance. |
Notification Event Alert on Version Issues |
Triggered when there is a version mismatch. |
Horizon adapter collection time is going beyond default threshold limit |
Triggered when the adapter collection time goes beyond the threshold limit. |
Average Application Session Helpdesk API response time above threshold |
Triggered when the Application Session Helpdesk API response time is above the threshold. |
Average VDI session Helpdesk API response time above threshold. |
Triggered when the Average VDI session Helpdesk API response time is above the threshold. |
Average RDS desktop Session Helpdesk API response time above threshold. |
Triggered when the Average RDS desktop Session Helpdesk API response time is above the threshold. |
Notification Event Alert on Help desk API Failure |
Triggered when the call to the Help desk API Fails. |
Notification Event Alert on Configuration Issue |
Triggered when there is a Configuration Issue. |
Either the Horizon Pod or the managed vCenter Server is not monitored by the vRealize Operations Cloud Instance |
Triggered when either the Horizon Pod or the managed vCenter Server is not monitored by the vRealize Operations Cloud. |
Number of Orphaned Objects is greater than 0 |
Triggered when the Number of Orphaned Objects is greater than 0. |
Data collection failed on the Horizon Connection Server |
Triggered when the Data collection fails on the Horizon Connection Server. |