Device Report Monitoring

Devices generally operate on a known reporting schedule, where there is an expectation that the device should report at a minimum within a set time period. For example, a device may be set to report every 12 hours while stationary, and every 30 minutes while in motion. In this example, we would expect to see a device report at least every 12 hours, if not more often.

To better track Devices that are in service, a reporting interval may be set on the devices to set a warning and an alert threshold. In the example above, it may be useful to set a 24 hour warning interval on the device, to allow for periodic missed reports, and a 48 hour alert interval when it has missed multiple successive report periods.

When configuring a device the reporting interval warning and alert thresholds (in minutes) may be set. If set, the system will automatically check from the last report received from the device to determine if an issue should be raised.

An example device witha reporting configuration is shown below.

In this example, there is a 60 minute warning on reports received, and 120 minutes configured for the warning to be escalated to an alert. For many types of devices these thresholds would be far too low, and the specific device configuration should be used as a basis for these settings. To avoid clutter and distractions, it is recommended to allow at least a missed report or two before raising a warning.

On the details screen we can see an alert for this device has been automatically created, and the user may click through to the alert to view the details.

If an alert has been raised and the device reports once again, the alert will be automatically closed, although the alert will remain in the account history.