{"id":600,"date":"2019-09-11T13:15:02","date_gmt":"2019-09-11T13:15:02","guid":{"rendered":"https:\/\/uptimerobot.com\/blog\/?p=600"},"modified":"2025-11-13T15:02:16","modified_gmt":"2025-11-13T15:02:16","slug":"new-feature-heartbeat-monitoring","status":"publish","type":"post","link":"https:\/\/uptimerobot.com\/blog\/new-feature-heartbeat-monitoring\/","title":{"rendered":"New Feature: Heartbeat Monitoring (Pro Plan)"},"content":{"rendered":"

Uptime Robot<\/strong> can already check the status of servers\/devices who have public IPs with its ping and port monitoring feature.<\/p>\n

Yet, there are many other servers\/computers\/devices that are inside an intranet (but connected to the internet) and need to be monitored<\/strong>.<\/p>\n

Heartbeat monitoring<\/h3>\n

It is now possible to monitor such endpoints<\/strong> using\u00a0heartbeat monitoring.<\/p>\n

The feature works in an opposite way\u00a0compared to other monitoring types.<\/p>\n

Uptime Robot<\/strong> provides a unique URL for each heartbeat monitor created and expects the monitored item to send regular requests to this URL.<\/p>\n

Once a regular request doesn’t arrive on time, the monitor is marked as down.<\/p>\n

\"Heartbeat<\/p>\n

Heartbeat monitoring is not only ideal for monitoring servers\/computers inside an intranet but also a great fit for monitoring the health of the regular\/cron jobs your website\/app may be performing<\/strong>.<\/p>\n

As an example<\/strong>, if your app runs a cron job which deletes the old logs every 10 minutes, you can update the code to send a HTTP request to the heartbeat monitor’s URL once that cron job\u00a0is ran and know that the cron job may be having problems if the heartbeat monitor is down.<\/p>\n

How to use the feature?<\/h3>\n

Heartbeat monitoring is\u00a0available in the Pro Plan<\/strong> and it works with steps:<\/p>\n