We have a SNMP CPU Load sensor on a critical server and all cores spiked to 100% at the moment that the sensor caught it. This immediately sent the Down notification to our ticketing system. Even though I have it set to:
Set sensor to warning for 1 interval, then set to down (recommended)
in the sensor settings. The scanning interval is 5 minutes. Logs show a trigger activated roughly a minute later. I would expect another check to fail after entry 1), then a trigger.
2) 6/19/2016 3:33:01 PM SNMP CPU Load Notification Info State Trigger activated (Sensor/Source/ID:54776/0/1)
1) 6/19/2016 3:31:57 PM SNMP CPU Load Down 100 % (Total) is above the error limit of 95 % in Total