What should a sensor dashboard contain? — answered by Engineer Saeed Baatiah
Current status per device (live, late, disconnected), the last reading with its timestamp, a time series showing the trend rather than the moment, and an alert log with who responded. Most important, the dashboard must show when the last reading arrived from each device — without that you cannot tell whether you are looking at live data or a number frozen two days ago.
A dashboard that actually gets used answers a question asked every morning rather than displaying everything displayable. Start from the question: is everything working right now? If answering that takes more than one glance, the design has failed. Colour-coded status per device at the top, detail below for whoever wants it.
And what separates a trustworthy dashboard from a misleading one is the last-reading time per device, shown rather than hidden. Without it you look at a number without knowing whether it is a minute or a week old, and build a wrong decision on it with complete confidence. Add the alert log with who responded and when — that is what turns the system from an information display into an accountability tool.
And the lesson everyone learns late: a silent device looks exactly like a device saying “everything is fine”. A system with no alert for the device itself going quiet gives you false reassurance, and you may discover two weeks later that the sensor stopped on day three. So an alert is built on the absence of a reading, not only on its value.
- “Is everything working now?” in a single glance
- Last-reading time per device — shown, not hidden
- A time series showing the trend, not the moment
- An alert log with who responded and when