Live values, freshness and gaps
Tell recent readings, stale readings and missing device contact apart.
On this page
What you need
A monitor with a configured reporting interval.
How to do it
- Read the latest value and its measurement time in the monitor.
- Compare the expected reporting interval with the last reading and heartbeat.
- Open history to see when readings stopped or resumed.
Good to know
A heartbeat is a device check-in, not a measurement of every component. It can arrive while individual readings fail. Numerical freshness normally allows twice the expected interval, with a minimum of 60 seconds.
Stale or unknown does not prove that a device is down. A connection problem can have the same appearance. Use missing-data or heartbeat rules for notifications.
If something goes wrong
Check the sender and connection first. A gap is not a zero and should not be repaired by sending made-up readings.
Related guides
- Explore measurement history
Explore readings in charts and tables for a period you choose.
- Alarms for missing data and device heartbeats
Be notified when readings or device heartbeats stop arriving.
- MetriBeacon Agent
Install the agent on your own machine and connect it to a monitor.