A user created a PowerShell script to check if a machine is running MS Defender Endpoint in EDR Block Mode and asked about setting up a trigger for alerts. Another user suggested using event log entries to trigger actions, citing a thread discussing it on the ControlUp Community Slack. The original script is provided in the discussion for reference and the user updates it to address false positive reports. The final version of the script is tested and confirmed to work.
Read the entire article here...
Triggers Related Training & Support Archives
Triggers training and support-related archives from inside the ControlUp Community on Slack.
Using ControlUp Triggers to Restart VMs with Pending Updates in Citrix
There is a question about using ControlUp Triggers to restart a VM when the user count reaches 0. There is a trigger set up to check the user session and reboot, but the check pending update condition is not working. It is clarified that the update referred to is for a master/golden image for Citrix. The CVAD pending image update column is suggested as a possible solution. A screenshot is provided for reference.
Read the entire article here...
Read the entire article here...
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 article here...
Read the entire article here...
Running long scripts in ControlUp and its behavior
A user asked about the behavior of ControlUp when running long scripts. It was clarified that if the same script is rerun before the first one finishes, a separate process will be started and the scripts will run one after another. It was also mentioned that this process will soon be automated and trigger only runs daily if needed. This was done to prevent running the scripts manually too aggressively.
Read the entire article here...
Read the entire article here...
Setting Up Alerts for SQL Always On Availability Group Failovers
A user asked for help with setting up an alert for a customer's SQL Always On Availability Group. Suggestions were made to use a PowerShell script or a scheduled trigger using the Edge DX agent. It was eventually resolved with the use of a PowerShell script that runs every 5 minutes and checks event logs for specific event IDs. No incidents are generated due to the potential scale of scheduled triggers.
Read the entire article here...
Read the entire article here...
Implementation of ControlUp monitoring for specific failed events
A user is looking to use CU to monitor their CA server for specific failed events, and wants to know if the trigger will work for each event. The trigger will only work for Warning or Error events, and one way to test it is by using a PowerShell script to generate a similar event on a machine with the CU agent installed. The script to create a test event is also provided. The event source must be created first if it does not already exist.
Read the entire article here...
Read the entire article here...
Using ListOfColumns Template Variables in ControlUp Triggers: A Helpful Tip and Exciting New Feature in the Works
Users discussed using ListOfColumns template variables for triggers and the impact of using them. One user shared an example of encapsulating the template with ListOfColumns to use multiple metrics in a trigger. Another mentioned that ListOfColumns can be replaced multiple times and added a warning about this. Another expressed excitement about the potential uses of this feature. The discussion also touched on the possibility of seeing the top 50 biggest files that were written and a suggestion for running a follow-up script to enrich the data. One user mentioned that the developer responsible was not available at the moment, but that more information would be shared soon and a real-time disk monitor was already available. It was suggested that the user hang on until Monday for a cool invite.
Read the entire article here...
Read the entire article here...
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 article here...
Read the entire article here...
How to Troubleshoot ControlUp Monitor Script Actions Not Firing
A user encountered an issue with script actions not firing as expected on a ControlUp Moniter. This led to a discussion on potential solutions and troubleshooting steps, including checking the script location and examining monitor logs. The user ultimately decided to look into the issue further when they have access to the customer environment. Troubleshooting steps and suggestions were provided by other members in the Slack discussion.
Read the entire article here...
Read the entire article here...
Troubleshooting Trigger for D:\ Drive Alert
A user asked for help with a trigger - they were trying to set an alert for when their D:\ drive goes below 500 GB, but the specified trigger was not working. Another user provided a solution and promised to post screenshots. The solution involved changing the File System Path to D:\*
Read the entire article here...
Read the entire article here...