Opening a war room from a silent heartbeat
Like Vendor Status Watch, there is no webhook payload to configure here. A heartbeat's silence is detected by a background sweep inside Landfall, reading state your own registered heartbeat already carries — see Heartbeats for how to register one and ping it.
How it works
A heartbeat is considered silent once its last-seen time (or, if never pinged, its registration time) is older than its configured expected interval plus grace period. The very next sweep pass that finds it silent opens an incident naming which heartbeat went quiet and for how long — reusing the same underlying open/attach/repeat/recovery mechanism every other automated source in this product uses (see Integrations architecture) — there is no separate, heartbeat-specific incident type.
There is nothing to opt into beyond registering the heartbeat itself (Heartbeats) — a silent, registered heartbeat always opens an incident; there is no notify-only mode for this source.
One continuous episode, one incident
A heartbeat's own silence-start time is the attach identity: repeated sweep passes over the same still-silent heartbeat attach to the one incident (in fact, an unchanged silence window is a true no-op — nothing new is appended at all) rather than opening another. A resumed ping is recorded on the incident as a recovery the moment it arrives, without waiting for the next sweep and without closing the incident — deciding the underlying problem is actually fixed stays a human's call, exactly like every other automated source. Closing the incident while the heartbeat is still silent is treated as ending that episode: the very next sweep pass opens a genuinely new incident, by design — a dead-man's-switch that could be silenced without being fixed would defeat its own point.
Knowing the sweep itself is healthy
GET /o/:slug/heartbeat-sweep/coverage reports when the sweep last ran and whether that is recent enough to trust — silence in your incident list is never allowed to look the same as "the sweep stopped running."
Reference
| Field | Value |
|---|---|
| Trigger origin | Internal (Landfall's own sweep) — not a webhook, no inbound route |
| Configuration | None beyond registering the heartbeat — always opens an incident when silent |
| Sweep interval | Every 5 minutes |
| Attach identity | The heartbeat's own silence-start anchor (last-seen time, or registration time if never pinged) |
| Recovery | Recorded on the incident the moment a ping arrives; never auto-resolves it |
| Coverage | GET /o/:slug/heartbeat-sweep/coverage |