Risks, Limitations and Assumptions

  • App can handle Critical/Recovery failure notifications for the following two cases when user enables App Failure Notifications in configuration
    • Connectivity Exception
    • Authentication Exception
  • App will send any duplicate/repeat failure alert notification for every 6 hours.
  • Metrics can be used to monitor Hypervisor resources and can generate alerts based on the threshold values.
  • We have provided the provision to give Citrix Hypervisor Host IP Address or Hostname and Port in configuration, but hostName provision will work only if the host name resolution works.
  • This app supports only Classic and NextGen Gateway. Not supported with Cluster GW.
  • Component level thresholds can be configured on each resource level.
  • Latest snapshot metric support from Gateway 14.0.0.

Classic App Xenserver to Citrix Hypervisor SDK App

If Classic App Xenserver was Installed, follow the below process to use Citrix Hypervisor SDK app to get the resources reconciled with the Classic App.

Troubleshooting

  • Ensure all the prerequisites mentioned are met
  • When Citrix Hypervisor integration fails to Discover / Monitor, please do below troubleshooting steps
    • Check if any alerts generated on Citrix Hypervisor Pool or on the gateway or any error logs in vprobe.
    • If the error/alert is related to End Device Connectivity or Authentication issue, try to check reachability of end device from gateway using following commands:
      • try ping with IP Address provided in configuration ping
      • try telnet using telnet
    • If you see any API failure in vprobe logs please run that particular API.
  • When any of the metric is not getting in the Citrix Hypervisor Monitoring. Please check the below documentation and make sure to met the condition: https://docs.xenserver.com/en-us/citrix-hypervisor/monitor-performance.html