Why Use AlertBot Over Installing Monitoring Software?
There are various reasons that make installing and running your own monitoring software a bad choice. The follow outline explains each one in detail.
Server Failure Results in No Alerts - If you install and run the monitoring software on the same server that you are monitoring and the server locks up, then so will the monitoring software.
AlertBot does not suffer from this problem because it does not need to install anything on your server and therefore your server failures will not impact our ability to alert you.
Local Network Failure Results in No Alerts - If you install and run the monitoring software on a separate server within the same network where you are monitoring servers, you have the following two problems. First, if the local network fails, the monitoring software would detect the failure but not be able to send the alerts because it is also connected to the same failed network. Secondly, if the hosting facility’s internet connection fails, your monitoring software would not detect it because it does not communicate through those internet connections for its testing. Even if it was able to detect the failure, it would not be able to send the alerts because the internet connection it needs is not available.
AlertBot does not suffer from this problem because it is not located on your network. Since we are located on a couple different networks around the world, failures on your local network and to your internet connections have no impact on our ability to detect them and to alert you.
2nd Location ISP Failure Results in No Alerts - If you install and run the monitoring software from a different location, you have the problem that if the internet connection (ISDN, DSL, or DialUp) fails at that location, then the monitoring software would not be able to get out to test the servers at the other location.
AlertBot does not suffer from this problem because it has Testing Stations located in multiple geographic regions around the world. If the internet connection at any of these locations failed, your server would continue to be tested from our other locations automatically.
Monitoring Software/Server Failure Results in No Alerts - if the software or server where you are running your monitoring software fails, it may be weeks before you even realize it unless someone is constantly checking that server to make sure the monitoring software is still running properly.
AlertBot does not suffer from this problem because our systems have been designed with a high level of redundancy. This means that even if some of our Test Stations failed, your website and server would continue to be monitored from our other healthy Test Stations automatically. Furthermore, even if there was a failure drastic enough to interrupt our service, we have an embedded network of internal alerting that would have one of our technicians fixing the issue within seconds.
Very High Cost - Besides all of the obvious problems with installing and running your own monitoring software described above, it would also be very expensive for you to run your own monitoring software. For starters, you must license a very expensive monitoring software package. Then you would need to purchase a server to run the monitoring software on. These two things alone would easily cost at least $2000, not to mention the labor costs involved in having an employee install it and maintain it over time.
With AlertBot, there are no upfront costs and the monthly service fee is so low that you could run the AlertBot service for many years before you would ever break even with purchasing your own monitoring software.
Server Failure Results in No Alerts - If you install and run the monitoring software on the same server that you are monitoring and the server locks up, then so will the monitoring software.
AlertBot does not suffer from this problem because it does not need to install anything on your server and therefore your server failures will not impact our ability to alert you.
Local Network Failure Results in No Alerts - If you install and run the monitoring software on a separate server within the same network where you are monitoring servers, you have the following two problems. First, if the local network fails, the monitoring software would detect the failure but not be able to send the alerts because it is also connected to the same failed network. Secondly, if the hosting facility’s internet connection fails, your monitoring software would not detect it because it does not communicate through those internet connections for its testing. Even if it was able to detect the failure, it would not be able to send the alerts because the internet connection it needs is not available.
AlertBot does not suffer from this problem because it is not located on your network. Since we are located on a couple different networks around the world, failures on your local network and to your internet connections have no impact on our ability to detect them and to alert you.
2nd Location ISP Failure Results in No Alerts - If you install and run the monitoring software from a different location, you have the problem that if the internet connection (ISDN, DSL, or DialUp) fails at that location, then the monitoring software would not be able to get out to test the servers at the other location.
AlertBot does not suffer from this problem because it has Testing Stations located in multiple geographic regions around the world. If the internet connection at any of these locations failed, your server would continue to be tested from our other locations automatically.
Monitoring Software/Server Failure Results in No Alerts - if the software or server where you are running your monitoring software fails, it may be weeks before you even realize it unless someone is constantly checking that server to make sure the monitoring software is still running properly.
AlertBot does not suffer from this problem because our systems have been designed with a high level of redundancy. This means that even if some of our Test Stations failed, your website and server would continue to be monitored from our other healthy Test Stations automatically. Furthermore, even if there was a failure drastic enough to interrupt our service, we have an embedded network of internal alerting that would have one of our technicians fixing the issue within seconds.
Very High Cost - Besides all of the obvious problems with installing and running your own monitoring software described above, it would also be very expensive for you to run your own monitoring software. For starters, you must license a very expensive monitoring software package. Then you would need to purchase a server to run the monitoring software on. These two things alone would easily cost at least $2000, not to mention the labor costs involved in having an employee install it and maintain it over time.
With AlertBot, there are no upfront costs and the monthly service fee is so low that you could run the AlertBot service for many years before you would ever break even with purchasing your own monitoring software.
Updated on: 10/24/2022
Thank you!