[August 26, 2019]

In version 0.9.77 we’re introducing a new type of Uptime Monitor which will use reverse monitoring in order to keep track of your server’s uptime.

Here’s how it works:

Instead of our monitoring locations pinging your server to determine its online status, this Uptime Monitor will use our Server Monitoring Agent (installed on your server) to send data to our platform every minute. If the Server Agent stops sending data, then the Uptime Monitor will be considered as being down and you are notified of its downtime.

Please read the full documentation here:

Usage cases:

  • This type of Uptime Monitor can come in handy if your servers are not directly reachable from the Internet, such as behind a NAT or behind a load balancer.
  • Another use for such an Uptime Monitor would be if you do not wish for our monitoring locations to constantly ping your server in order to check its uptime status.

Please note:

This type of reverse monitoring is not as precise as our other Uptime Monitor types where the uptime status is checked simultaneously from multiple of our uptime monitoring geo-locations (ie: where there would need to be multiple points of failure for a false positive). With the ‘Server Agent Monitor’ type of uptime monitoring there’s going to be just one single point of failure that will determine the uptime status (ie: if your server cannot ping our endpoint for any reason, the uptime monitor will be declared as offline). Because of this we recommend that you go with the default 3 minutes timeout, which would give your Server Agent 3 tries to send data before declared as being down.

Furthermore, there will be no Location Fail Log or Network Diagnostics being collected for this type of monitoring.

If you experience any issues with this new feature, please open a support ticket on our website and let us know about it.