WDT.io You alert end of alert Your Webserver kick Your Server kick Version Control Continuous Integration kick 2 kick 1 start push

the uptime monitor for everything

our locations
Fundamentally, WDT.io is HTTP based and works three ways. Outbound with a schedule, inbound with a schedule, and inbound without a schedule (on-demand). Electronic watchdog timers are kicked to prevent them from going into alert. WDT.io uses the same concept and terminology. A GET or HEAD request is the kick. Like a ping.

An outbound watchdog timer kicks your server on a regular schedule. When your server can't be kicked, i.e. is unreachable, you get notified. Great for monitoring websites and other HTTP servers.

An inbound watchdog timer waits for kicks from your server. When an expected kick is not received, you get notified. Great for monitoring cron jobs and other scheduled tasks.

An on-demand watchdog gets started by a kick from your server, and then stopped by a second kick. When the second kick is not received, you get notified. Great for monitoring transactions.

To monitor a cronjob, for example, simply add the green script to the crontab. cURL kicks the inbound watchdog timer "hourly-task". If hourly-task.sh fails or doesn't even get started, the watchdog timer will alert you.

0 * * * * hourly-task.sh && curl k.wdt.io/hourly-task