Why it matters
Missed heartbeat matters because teams need a precise shared meaning for a heartbeat that did not arrive within the allowed schedule and grace period. Vague language turns incidents into arguments about words instead of fixes.
When everyone uses the same definition, alerts, status updates, and post-incident reviews stay aligned.
How it works
In practice, a heartbeat that did not arrive within the allowed schedule and grace period shows up as a concrete signal you can measure or communicate. Operators define what good looks like, watch for deviations, and record what happened when expectations break.
The useful version of missed heartbeat is operational: it changes who gets notified, what customers see, or which metric a team reviews after an incident.
Practical example
Imagine a team operating around backup heartbeat missing after 02:15 UTC plus grace. When observed behavior stops matching the definition of missed heartbeat, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Missed means the server is on fire
That reading usually collapses distinct ideas into one slogan. Keep missed heartbeat tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
A missed heartbeat means the expected signal did not arrive. Investigate the job path.