Uptime Monitoring vs Heartbeat Monitoring
People think an uptime check will notice a failed nightly job, and it will not. An uptime check knocks on a service and waits for an answer. A heartbeat monitor waits for the job to knock on its door. A backup that never ran has no door to knock on, so only the missing heartbeat shows it.
Uptime Monitoring
A check from outside, each minute, that a site still answers. It warns you when it stops.
Uptime monitoring checks from the outside that a site or service answers. A tool sends a request every minute or so, often from several places in the world. If the answer is wrong, slow or missing, it sends an alert. It also keeps a record of the share of time the service was up. That share is called uptime, and it is often shown as a percentage.
Heartbeat Monitoring
An alert that fires when a job stops checking in. It catches silent failures.
Heartbeat monitoring waits for a job to check in on time, and raises an alert when it goes quiet. The job sends a small ping each time it finishes, such as after a nightly backup. The monitor knows when the next ping is due. If none arrives, something stopped, even though nothing reported an error. It catches the failures that make no noise at all.
In one line
- Uptime Monitoring
- A check from outside, each minute, that a site still answers. It warns you when it stops.
- Heartbeat Monitoring
- An alert that fires when a job stops checking in. It catches silent failures.