Troubleshooting a Stopped Trigger in ControlUp

A user is experiencing trouble with a trigger that suddenly stopped working. They shared a screenshot of the trigger and asked for suggestions on how to improve it. Other members chimed in and offered potential solutions, such as checking the trigger’s configuration in PowerShell and verifying the versions. A script to test triggers was also suggested. The user has resorted to using a PS script via scheduled task for alerts. They also checked the Web Interface, which reported a server as Not Active even though it was running in SGP. They requested a script to test triggers. They were also asked what the Get-BrokerController showed for those brokers.

Read the entire ‘Troubleshooting a Stopped Trigger in ControlUp’ thread below:

Hi All, I’m having a little trouble with a trigger that frustratingly worked previously but has for some reason stopped working at all.

I created the attached trigger to monitor our CVAD servers for when Citrix Licencing goes into Supplemental Grace and then sent a API request into out ticketing system. Over the bank holiday we’ve had two machines go into SGP and no alerts have been generated.

I’ve also tweaked the alert to match the second screenshot but this hasn’t made a difference either despite the machines still being in SGP, can anyone shed any light on why this would suddenly stop working or offer any suggestions for a better way of capturing the information.

The first screenshot might not be configured as intended? The from and to state are the same. That transition would never happen.

Having said that, easiest way to verify that the trigger is working as intended is probably Powershell. @member has a script that can test triggers.

Alternatively, you can check the data in the web interface.

Last but not least, what is the scope of that trigger? Is it the entire organization or is it limited to certain folders?

An edge cases that is unlikely your issue is mismatch of versions. A customer in the past was creating triggers with a console that was a significantly different version than the monitors. The format of triggers changes every once in a while. To support new functionality. If the console creates a trigger in a different format/version than what the monitor expects, it might lead to unexpected results.

Let me know if you are still interested in the script that can test triggers. But as Dennis pointed out, the From/To are the same.

@member they are different states 🙂, the optional state is checking for "is Not Active" the second is checking for "is not Not Active" which would cover any state that is Not Active such as in SGP, or lost connection licence server etc.

I even removed the optional criteria and tested as well as using the Citrix licencing dropdown instead of machine and had the same outcome.

As I say it was working fine and alerting when we went into SGP and when the licence server was offline due to patching reboots etc but suddenly stopped across the board.

I’ve now resorted to using running a PS script via scheduled task on the boxes to send an alert that way.

I have just checked the Web Interface and this is reporting the server as Not Active however the machine is currently running in SGP so that would indicate that CU is not detecting the state via DX or DEX.

@member I wouldn’t mind a copy of the script if you don’t mind as being able to test triggers in general would be a great tool.

what does Get-BrokerController show for those brokers?

Continue reading and comment on the thread ‘Troubleshooting a Stopped Trigger in ControlUp’.  Not a member? Join Here!