[-]
  
  
[-]
  
  
  
  
  
  
  
 
 
[-]
  
  
  
  
[-]
  
 [+]
  
[-]
Monitoring
  
 [+]
 [+]
 [+]
  
[-]
Monitoring guides
  
  
[-]
Templates
  
  
  
[-]
Cloud monitoring
 [+]
  
  
 [+]
Kubernetes
[-]
Network checks
 [+]
  
  
  
[-]
 [+]
  
  
  
  
  
  
 [+]
 [+]
 [+]
 [+]
[-]
CounterMeasures
  
 [+]
 [+]
  
  
[-]
Panopta OnSight
 [+]
 [+]
[-]
SNMP
 [+]
  
[-]
Alerting
 [+]
 [+]
 [+]
 [+]
 [+]
[-]
Reporting
  
  
  
[-]
Maintenance
  
  
[-]
API
  
  
  
  
[-]
Users, Groups, and Authentication
 [+]
  
  
  
[-]
Billing and Payments
  
  
  
  
  
  
 
[-]
  
  
  
  
  
  
  
  
  
  
  
  
Updated on 7/26/2019
Online Help
How do you minimize false alerts?
Direct link to topic in this publication:
  • FAQ
  • ยป
  • How do you minimize false alerts?

Our system uses a custom algorithm to confirm every outage before beginning any notifications. After we first detect a failed service check, confirmation checks are performed from a number of geographically nearby monitoring locations, and only after a quorum of these locations confirm the outage does the notification process begin.

Once the service has been restored and is returning successful checks, the same process is repeated to confirm the resolution. With this approach, any spurious failures are eliminated and alerts are only sent on real, confirmed problems.

Due to the design of our system, the entire confirmation process is handled quite quickly, typically within 20 seconds of the initial failure detection.