Articles on: Technical

How Does AlertBot Eliminate False Alerts?

When a test failure is first detected at one of our Test Station, a follow up test is scheduled one minute later to validate the failure from a different test station in a different geographic region of the world. If that second Test Station also reports the same test failure, then our systems consider it a confirmed failure and start the alerting process.

Since these two Test Stations run completely independently of each other and are located in different regions of the world, our systems are able to draw two important conclusions about the test failure.

The test failure could not have been a result of an internal error at the first Test Station. We know this because the second Test Station operates independently of the first Test Station and reported the same test result. Any internal error at the first Test Station would not have influenced the test results from the second Test Station. For this reason, if the second Test Station reports the same test failure as the first then it must really be a result of the customer's website or server.

The test failure could not have been a result of a regional network problem in the city of the first Test Station. We know this because the second Test Station operates in a different geographic region of the world and is on a totally different local and regional network. Any regional network problems at the first Test Station would not have influenced the test results from the second Test Station. For this reason, if the second Test Station reports the same test failure as the first, then it must really be a result of the customer's website, server, or network.


Related Links
Are There Any Hardware/Software Requirements?
What Happens if AlertBot Goes Down?
AlertBot System Redundancy and Scalability Explained
Receiving an Alert and Discovering Your Site is Fine

Updated on: 10/24/2022

Was this article helpful?

Share your feedback

Cancel

Thank you!