Quote:
Originally posted by joechip
I can see a few possible problems with a free barebones monitoring service like this:
What happens after the network you're hosting on goes down and comes back online- Are a zillion emails in the queue waiting to go out to every host and webmaster you are monitoring?
What happens if Choker's provider has a problem getting to a particular network? Do you have anything in place to pinpoint where the real problem is, or does the host being measured get blamed for *any* type of problem on the internet between Choker's place and their own network?
To do this sort of thing right you need to be multi-homed, and preferably multihomed at a number of strategic monitoring points spread around the internet. You also need a reasonably intelligent 24/7 human staff to determine when outages are real, or just due to network problems that are unrelated to the network hosting the measured sites.
Take a look at Keynote if you want to see what a decent website performance monitoring service looks like.
|
This system does not ping the sites it monitors like traditional monitoring services. Every 5 minutes my server contacts the plugin on the domain being monitored and retrieves all the data. So my server is not really monitoring your server. Your server is monitoring itself. My server jsut gets that data every 5 minutes and displays it all. This method takes care of most of the concerns above.