will be discontinued. We will stop our services at the end of September 2019. Please switch to another monitoring solution. From personal experience I can recommend Prometheus as a self-hosted solution for all kinds of monitoring or for hosted (or self-hosted) simple cronjob monitoring. For hosted website monitoring you could use UpTimeRobot.


Pings allow you to monitor periodic jobs. You configure your application to send a GET request to PiDAR and we will keep track of the requests you send. In PiDAR you specify a timeout interval for each ping and if we do not receive a ping from you within the timeout period, you will get notified.

Creating a new Ping

To create a new ping, go to the pings overview page (login required) and press the button Create new Ping. Choose a name for your ping and an interval during which you expect it to run. You can define a grace period if you do not want to send out notifications immediataly after a timeout. In this case, we will additionaly wait for another ping during the grace period. If a ping does not arrive within the grace period, you will receive a notification. You can set the grace period to zero if you do not need it.

Optionally, you can define tags for your ping. Tags are used to structure pings into groups and can be used to create public dashboard. For example, at pidar we use the tag pidar to create a dashboard of public monitors.

When the ping has been added you will be redirected back to the ping overview page. On the ping overview page you will see the Ping URL that was generated for you. You have to send GET requests to this URL from your application. Try visiting the URL with your browser and you should see that the Last Notification column in the overview will change.

Managing Pings

After you have created your first pings, you will see a list of all of them on the pings overview page. It will also display the last time we received a notification for this ping and highlight its state according to your timeout definition.

The Pings overview page shows all your pings on one view

By clicking on the name of a ping you can edit its attributes. You can change the name, the interval and grace period as well as the tags. The ping URL cannot be changed. Its created automatically by us and will be static over the full lifetime of your ping.

Ping Aliases

It is possible to define aliases for pings. These aliases will be tied to your username and you can use each alias only for one ping. If you define aliases for a ping, you can send notifications to your pings either via our unique URL or via your alias URLs.

Aliases can be useful if you want to use a lot of different pings in an external service and do not want to create a mapping table from your external names to our GUIDs. For example, you might want to create one ping for each user of your service. In this case, you can define the username of your user as an alias and then query the alias URL via the username instead of having to store the PiDAR GUID for each of your users.

Ping aliases will be listed next to the standard ping URLs in your ping dashboard. You can add them when creating a new ping or when editing an existing ping.

Attention: Ping aliases could increase the risk of an attacker calling your pings and thus disable your alerts. GUIDs will be harder to guess most of the time than common use cases for aliases. If you are worried about other people sending notifications for your pings, you might want to continue using GUID URLs only.