Setting up PulseChecks

A guide on monitoring non-webservers or periodical scripts with Semonto's PulseChecks.

Screenshot of contact groups in Semonto

You can use PulseChecks to monitor servers that are not accessible over the internet, database servers or behind a firewall for example. Consider it like measuring the heart rate of a server. You can also use PulseCheck to monitor periodical scripts such as backup-tasks.

The idea is actually quite simple: Your server needs to give a pulse to our server (just by calling a specific url). If your server does not give a pulse on time, Semonto will alert you.

Creating a PulseCheck

When you create a PulseCheck, Semonto will create a unique URL which you need to call on your server.

You can specify the time-out immediately and you can select a specific server from Semonto that should check for the pulse by your server. When you set the time-out, make sure to provide a bit of overlap. For example when you use a PulseCheck for a back-up script, set the interval for 25 hours or when you monitor a database server every hour, set the time out to 90 minutes.

PulseChecks Details

When creating a PulseCheck you only have to provide a name and a time out. The time in which the next pulse should be received by Semonto. We also provide the option to select a specific server, best is to select the server nearby.


It is important to assign at least one Contact Group to a PulseCheck to alert someone when it expires. This can be done in the edit view of a PulseCheck.

You can assign multiple contact groups to a PulseCheck to have fine grained control who to contact when the pulse expires. You can read more on Contact Groups this guide.


In the details view you can find all the information from the PulseCheck. Also the IP-address from the last pulse and the frequency of the pulses.


If you have a backup-script that runs daily and you would like to be alerted when the backup-script did not run for more than 25 hours.

Create a new PulseCheck and Semonto will generate a PulseCheck URL, for example:
When the PulseCheck has been created and is ready (this can take up to 15 minutes and can be checked at the details page of the pulse), you can integrate a call to this PulseCheck URL in your script. Your script needs to call this URL when installed on your server and needs to call this URL within the time out.

For example in CURL:
curl --connect-timeout 5 -f ""

For example in PHP:
<?php $url = ""; $result = file_get_contents($url); //check $result ?>

Resolving issues

Results from calling the PulseCheck URL can be:

0: which means everything is okay.

Error 144: in this case you need to check if you have the correct PulseCheck URL and if the PulseCheck is synced yet (see the status at the PulseCheck details page).

When you need any assistance on setting up a PulseCheck on your server, feel free to contact us at