In this article I would like to explain status codes and other info provided in notification e-mails of Monitis for a services with HTTP checks.

HTTP protocol has the following types of error codes:

2xx – this codes indicate success

In recovery notifications you will often get 200 – OK HTTP response code, which means that the request was fulfilled.

4xx – codes are intended for cases in which the client seems to have errors

5xx – codes are intended for cases in which the server is aware that the server has errors

Most common errors of the above mentioned types are:

400 – the request had bad syntax or was inherently impossible to be satisfied

401 – the client should try the request with a suitable Authorization header

403 – the request is for something forbidden. Authorization will not help

404 – the server has not found anything matching the URI given

500 – the server encountered an unexpected condition which prevented it from fulfilling the request

Besides the above mentioned status codes during HTTP checks you will also get the following information:

Connection timed out after 10 sec. – which means that for some reasons monitoring server couldn’t conduct a check during 10 seconds

Connection refused – for some reasons monitored server refused the connection request from our monitoring server

Wrong response HTTP header received – monitoring server received a response with a wrong HTTP header

Connection lasted more than 10 seconds – which means that response has exceeded 10 seconds, which is set as a timeout for HTTP check

So here it is, we’re finished with HTTP checks and will discuss the other check types in the upcoming articles.