To measure realtime delivery latency and connection health for a Node.js e-commerce device-status dashboard, collect client receipts across reconnect and backfill. A connected dashboard can still be showing yesterday's truth: the first message after recovery may be old, even when the connection itself looks healthy.
Short answer: publish a timestamp with each status message, have the receiving client report its observed delay, and track that delay as a metric. Separate live delivery from recovery traffic, track connection health alongside it, and alert on a sustained trend rather than one slow sample. For a Node.js publisher, the decisive observation still comes from the client.
What page fired when the dashboard went stale?
Start the postmortem with that question.…