False Positive Checks are enabled for all devices by default.
The false-positive check helps to eliminate potentially false errors when there may have been a brief hiccup or network glitch that caused a single location to identify a false error.
False-positive checks are initiated when an active monitoring location detects an unsuccessful monitoring result. Upon detection, the location immediately runs several self-tests to verify network connectivity and then performs the tasks again to verify that the monitoring tasks really are unsuccessful. Once the failure has been verified, the state changes from Success to Failure and the system checks to see if there are any alerts that should be triggered based upon existing filters and schedules.
Immediately after triggering the first alerts, all active monitoring locations for this device are immediately queued to perform the monitoring task on this device.
Additional alerts will be triggered based upon the alert settings including filters, schedules, and time delays between alerts.
Alerts can be further refined by applying filters, schedules and time delays to the device.
False-positive checks may cause some delay in receiving alerts because an alert will not be sent until at least one additional monitoring agent has detected an unsuccessful result. Alerts may be delayed if the device is complex and takes a long time to complete all monitoring tasks.
Only disable false-positive checks if you require fast alerts upon the first detection and you are okay receiving false alerts when a single location encounters small errors that may be unrelated to the performance of this device.
See also: Troubleshooting false alerts.