Short answer: treat a heartbeat as evidence of recent contact, never as proof that every incident event reached every dashboard; for marketplace device status, use an ordered event stream with per-device sequence numbers, resumable cursors, and idempotent projection, while reserving WebRTC for sessions whose latency and peer-to-peer topology justify its operational cost.
That separation matters during incident response. A green pulse can arrive after an alarm was dropped, and a red pulse can reflect a sleeping radio rather than a broken device. The dashboard therefore needs two independently auditable statements: when the service last heard from the device, and through which event each viewer has advanced.
No single transport creates exactly-once delivery.
What should a realtime heartbeat monitoring dashboard guarantee during incident response?
The useful contract has three layers.…