Troubleshooting a Trigger in ControlUp for Unregistered Citrix VDA Machines

A user needed help with a trigger that should detect an unregistered Citrix VDA and trigger an OS reboot. They were wondering if the trigger needed to be tagged against the folder with the delivery controllers. Another user suggested trying switch from "uptime" to "triggerable uptime". This solved the issue, and the second user also explained the difference between "uptime" and "triggerable uptime" metrics. The user who originally asked the question also wanted to know how ControlUp checks for CVAD registration, as they were experiencing some false positives. The conversation ended with the user stating their issue with automatically resolving alerts when ControlUp detects that the machine is back to normal.

Read the entire ‘Troubleshooting a Trigger in ControlUp for Unregistered Citrix VDA Machines’ thread below:

Looking for some help/advice with this one if possible.

I have a trigger that should detect if a machine if a Citrix VDA unregistered and trigger an OS reboot providing certain criteria has been met (See screenshot), the script it triggers is basically set to run as CMD/BAT to run shutdown /t 0 /r /f.

For some reason this doesn’t seem to be triggering when I manually stop the Citrix desktop service to force the machine into an unregistered state, at the moment the trigger is only set against the TEST folder with the individual test box in so I was wondering if it could be because it also needs to be tagged against the folder with the delivery controllers in? Or have I just totally missed something here? 😄

In the web interface, what are the values for cvad registration, cvad maintenance, uptime and vm power state columns?

Also try switching from uptime to triggerable uptime in the trigger configuration

triggerable uptime seems to have done the trick, thank you so much for sharing.

For reference. Uptime is basically a virtual metric. It merely calculates the time difference between the boot time of the machine and . It doesn’t really exist.

Triggerable uptime is a real metric that is updated periodically in the underlying data.

@member thank you for the info, would you happen to know how CU checks the CVAD registration?

We have an environment with over 1200 VDA’s but for some reason over the last 2 days we’ve been getting what appear to be false positives as when we check the VDA’s are registered and there doesn’t appear to have been any loss in connection for users.

My issue is if it were an issue with the trigger surely it would generate an alert for 1200 VDA’s not just 200 or so?

We currently send a RestfulAPI into our ticketing system but I’ve not been able to work out how to auto resolve alerts yet if CU detects the machine is back to normal.

Continue reading and comment on the thread ‘Troubleshooting a Trigger in ControlUp for Unregistered Citrix VDA Machines’.  Not a member? Join Here!