Steps taken by Site24x7 to prevent false alerts
Site24x7 is committed to zero false alerts and we have numerous measures in place to make sure downtime alerts from Site24x7 are genuine. Site24x7 eliminates false alarms by applying the "False Alarm Protector". Threshold and Availability Profiles help the alarms engine to decide if a specific resource has to be declared critical or down. Configure Downtime Rules to reduce false alerts. Check out our blog on How to Eliminate False Alerts with Site24x7?
- Rechecks from alternate locations
We will report an outage only after the downtime is verified from alternate locations. When a website is found unavailable from one location, rechecks are done from other monitoring locations. If any recheck returns a positive response, the website will be considered as 'UP' and alerts will not be sent.
The rechecks usually happen from,
- Secondary Locations, if you have configured them in your account
- Randomly selected locations, if there are no Secondary Locations configured in your account
- Advanced Threshold Settings (Strategy)
' option in our threshold configuration gives you more control over Trouble or Critical alerts and avoid false positives. Apart from configuring the thresholds for the attributes, you can specify the number of polls or time interval in which the threshold must be continuously breached, or the average value of the attribute over certain number of polls or time interval that must be breached to initiate trouble status. Learn more
- Browser based check
After the rechecks are completed, a final check on the status of your website is done via a web browser. We will use a web browser to load your website and a screenshot of the response is stored. If the website is found available in this browser based check, it will be considered as UP and no alert notifications will be sent.
- Network Sanity Check to ensure our own network is fine
Before reporting on an outage, Network Sanity Check will make sure that our own network in the monitoring location is working fine, thus preventing false alerts due to any temporary network issues.
How to map the severity of alerts from Site24x7 in Moogsoft ?
By default, these are the corresponding severities in Moogsoft for alerts raised from Site24x7. Site24x7 Alert Status Corresponding Moogsoft Severity Up ...
Alert suppression at the monitor level – Achieve better protection against false alerts through monitor-level dependency configurations
A network outage usually triggers hundreds of alert messages and calls to multiple personnel. However, some of those notifications will likely be redundant. Without the proper alert configurations, an outage event could quickly burn through all your ...
Work-around to avoid false alerts in server monitoring
Use case: A server monitoring set up that has jobs running periodically throughout the day at unspecified times, and for an unspecified amount of time. As these jobs are running, they use up the server's CPU usage to 100%. This triggers false alerts, ...
Licensing for AppLogs Alerts
Every log type is treated as a monitor and any search query can be configured for alerting. Here's the number of search queries for which you can configure to receive alerts for free: Log size Number of free search queries 10GB 5 ≤ 100GB 10 ≤ 500GB ...
Configuring voice calls and SMS alerts for AppLogs
For the AppLogs Alerts that you configure in the AppLogs tab, you can set up email, SMS, voice calls, and instant messenger alerts at the monitor level. For example, if you want to configure email or voice call alerts for your Syslog monitor, edit ...