New Capability in ControlUp 9.2 to Monitor and Trigger VDA Registration in Real Time

A user asked for help with obtaining the current registration failure reason in ControlUp, similar to what is available in Citrix DaaS Monitor. @member mentioned that the upcoming 9.2 release will introduce a new capability to monitor and trigger on VDA registration state in real time. This will provide deeper insights and allow for automation actions to be taken against DDC or VDA.

Read the entire ‘New Capability in ControlUp 9.2 to Monitor and Trigger VDA Registration in Real Time’ thread below:

Hi All,

Question: How to get the current registration failure reason in ControlUp similar to what is being shown in Citrix DaaS Monitor?

In Citrix Monitor we can see detailed failure reasons like Contact Lost or Power Off. In ControlUp, xdFaultReason seems to only show a general type (e.g., Unregistered), and xdLastRegFail gives more detail but only for the last failure, not the current one.

Is there a way to pull the current registration failure reason in ControlUp (similar to Citrix Monitor), or is there another table/field I should query? XD_VDA, and Citrix Connection Failure log are what I tried until now.

hey @member maybe you can take this one?

The upcoming 9.2 release introduces a new capability to monitor and trigger on the Registration State of a VDA in real time. Whenever a (de)registration occurs, the monitor generates an internal registration incident that can be used to automate actions against your DDC (CVAD) or VDA (both CVAD and Citrix Cloud). In addition, deregistration events will now be enriched with Windows Events collected from the VDA, providing deeper insights beyond the basic deregistration reasons reported by the OData API

Continue reading and comment on the thread ‘New Capability in ControlUp 9.2 to Monitor and Trigger VDA Registration in Real Time’.  Not a member? Join Here!