A user asked about false alarms being triggered on failed machines, and it was suggested to check the Incident tab in the (old) console to see values and to change the trigger to dump all machines, folders, sessions and processes to CSV files in order to analyze the incident. Mitigation strategies such as setting the threshold to at least 1 min was suggested.
Read the entire ‘Mitigating False Alarms on Failed Machines’ thread below:
Does anyone have any experience of this alert triggering on false alarms for failed machines? Citrix Monitor shows no failed desktops, not 103.
Hey @member, check the Incident tab in the (old) console. There you can see the values. You can also change your trigger to dump all machines, folders, sessions and processes to csv files, so you can analyze later what happened at that moment in time.
false alerts can be mitigate by how long the threshold has to be in breach, False alerts can be a mail and in early says of using CU i got a lot of them setting the below setting to at least 1 min is a default for me most of the time
Continue reading and comment on the thread ‘Mitigating False Alarms on Failed Machinesin ControlUp’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers