Website availability monitoring

Website availability monitoring

« back to feature list

The basic monitoring feature of our system detects complete failures of websites—i.e. situations in which they are completely inaccessible.

These types of events are most often the result of infrastructural problems—a failure of the web server or connection.

website availability monitoring

How it works

Every minute we connect to the website's address and check the server response code, simultaneously measuring the response time.

If the response code is different from the correct one ("HTTP 200 OK") or you have to wait too long for a response ("Connection Timeout"), we register a failure and send notifications.

In order to exclude false alarms, we only report failures reported by at least three of our monitoring stations.

Configuration

All you need to do is enter the URL of the website and, if needed, change the default server response timeout (10 seconds).

You can also change the frequency of monitoring (1 minute by default), but we do not recommend this because less frequent tests of the website significantly reduce the effectiveness of monitoring.

website availability monitoring configuration

Other features

Availability monitoring can be used for more than just website monitoring. By changing the protocol/port, you can start monitoring the availability of:
  • any server (PING)
  • file server (FTP)
  • mail server (SMTP, POP3, IMAP)
  • database server (MySQL, MSSQL, PostgreSQL)
  • other (TELNET, SSH, DNS, CONNECT, SIP).

Additional information

Connections generated by availability monitoring are invisible to JavaScript-based traffic monitoring services—such as Google Analytics—meaning they won't disrupt your statistics.



« back to feature list