Why it matters
Late heartbeat matters because teams need a precise shared meaning for a heartbeat that arrives after the expected time but may still be within grace. 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 arrives after the expected time but may still be within grace 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 late 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 ping arriving twelve minutes late. When observed behavior stops matching the definition of late heartbeat, the team treats that change as a reliability event with a clear owner and next step.
Common misconception
Late and missed are identical states
That reading usually collapses distinct ideas into one slogan. Keep late heartbeat tied to observable behavior so the definition stays useful under pressure.
How Fajita handles this
Late heartbeats can indicate slow jobs. Tune grace periods with real runtimes.