This page has been robot translated, sorry for typos if any. Original content here.

We organize the monitoring of the health of the web server

Web servers on the Internet are like patients in a hospital room who need constant supervision. I almost didn’t look at it - my beloved server didn’t respond at all either, forcing the network ruler to excite the walk of creative ideas about the upcoming showdowns with equipment, provider, customers, management ... How to be? To non-stop to sit also on duty all night long near the computer? Or do manual monitoring from a remote machine? No, this is not our method. We will try to find something automated, affordable and also convenient. The Google network search guru, swallowing our request "website monitoring", gave a go-go Internet links to various resources offering their services in the audit district as well as analyzing the performance of web servers. Monitoring systems (in Basurmian language they are often called uptime-systems) are quite a lot - also paid, also free of charge. We will not consider the latter in any way due to the limited nature of their capabilities and the unwarranted labor of the service they provide.

So, it was decided - we choose a commercial monitoring system. What else should you look for? First, look at the presence of several monitoring checkpoints, preferably geographically distributed across different servers. Indeed, you must admit that it is foolish to procrastinate detailed and reliable statistics collected only from one computer (polling points). Secondly, take an interest in the list of services provided as well as services. This list can exist very extensive - from testing HTTP, POP3, IMAP4, FTP as well as other protocols, right up to controlling DNS and other services. Look at the capacity and the quality of the statistics provided - it will help to study the chronicle of the "ups and downs" of your servers over the entire fleeting interval of their monitoring. Additionally, in the end, thirdly, it is necessary to carefully approach the task of analyzing the usability of the system. Interrogating your servers, the system will generate a walk of various reports that you have to work with, and any conclusions will also apply.

Now we’ll try, based on the tips given above, to take some commercial service at random for testing.

For example, WatchMouse.

The first good news that catches your eye at once is a free 30-day period of using a full-fledged monitoring system. The far-sighted WatchMouse developers have acted quite cunningly, since the capabilities of their system bribe users, but abandoning the tidbit is quite difficult. What blah blah does this “observational mouse” allow? We list the items.

• Server analysis using multiple monitoring points located throughout the universe. A speck of a survey to eat even in Rio de Janeiro - Ostap Bender would be glad.
• Detailed textual and graphical statistics, including the ability to export data to Excel.
• Powerful event filtering capabilities.
• A variety of online network tools (Ping, Traceroute, DNS Query, etc.).
• Notification of events by e-mail, ICQ, SMS and access to statistics via WAP, using the capabilities of a mobile phone.
Can you imagine what amenities modern IT technologies provide? It’s scary to think that only one SMS message with information about the “crashed” web server can destroy the glamorous illusions of the system ruler in one moment and sit in a cozy cafe somewhere to drink good cool beer ...

Well, what is allowed to add more? In my opinion, we talked about all the main points and subtleties of choosing systems for monitoring. We only note that the bazaar of such tools is quite extensive, diverse and the choice is yours. In any case, it is better not to save information on statistics as well.