Health check
The Health check tab allows you to monitor the status of devices installed on units and quickly identify any deviations in their operation. You can track various metrics such as battery level, number and frequency of messages sent, voltage, ignition state, and more.
Configuring health check
To start monitoring the technical state of a device, follow the steps below.
- If the health check criterion you want to track requires a sensor, create it. See the required sensors in the List of criteria section.
- Find the required criteria in the list. By default, basic criteria are shown. If the required criterion is not in the list, click Add criterion and select it
- Specify the conditions for the customizable criteria. It can be the minimum or maximum allowed value or a range of values.
- For each criterion you want to track, specify how long the device must comply with a criterion to trigger an incident:
- 1 minute
- 10 minutes
- 1 hour
- 1 day
After that, the system starts tracking the health check criterion. If its conditions are met within the specified period, an incident is registered for the device.
If you change the criteria configuration on the Health check tab, new generated report tables show past data according to the new configuration.
Use of health check incidents in the system
You can manage the registered incidents in the following ways:
-
View the incidents in real time on the Dashboard tab. They are shown in the Device health check status block and in the dedicated blocks for each criterion. See more details on the Dashboard page.
-
Generate reports on incidents. See the Health check incidents table.
-
Trigger notifications with different system actions when the device status changes depending on the number of registered incidents. See the Device health check status notification type.
Disabling health check criteria
To stop monitoring a health check criterion, exclude it from the list. To do this, hover over the criterion row and click on the icon 
.
List of criteria
The Health check tab contains the criteria which you can use to monitor the device health. They are divided into two groups based on the source of data used for criterion tracking. Some of the criteria can be customized by specifying values for triggering the incident.
Sensors
The criteria in this group are tracked based on a sensor configured in the unit properties.
| Criterion | Description |
|---|---|
| Device battery level | Uses the sensor selected in the Device battery field on the Advanced tab of the unit properties. Tracks the device battery level. An incident is registered if the battery level is less than the specified value during the selected period. The default setting is less than 20% during 1 hour. Missing sensor data doesn’t trigger an incident. This criterion uses raw sensor data before filtering is applied and after applying the calculation table, validation, or expressions specified in the Parameter field of the sensor properties. |
| Voltage level | Requires a voltage sensor. Tracks the voltage of the onboard network, tracker battery, or any other voltage source. An incident is registered if the sensor value falls outside the specified range during the selected period. The default setting is less than 12 V and more than 13 V during 1 hour. For voltage, decimal values can be used, separated by a dot. If multiple sensors are available, each one is monitored. Missing sensor data doesn’t trigger an incident. This criterion uses raw sensor data before filtering is applied and after applying the calculation table, validation, or expressions specified in the Parameter field of the sensor properties. |
| Ignition off | Requires an engine ignition sensor. Tracks whether the vehicle ignition is on. An incident is registered if the sensor value remains “off” and doesn’t change to “on” during the selected period. The default period is 1 hour. If multiple sensors are available, each one is monitored. Missing sensor data doesn’t trigger an incident. |
| No changes in fuel data | Requires a fuel level sensor. Tracks whether there have been any changes in the values of the fuel level sensor. An incident is registered if the fuel level sensor values remain unchanged during the selected period. The default period is 1 hour. If multiple sensors are available, each one is monitored. Missing sensor data doesn’t trigger an incident. This criterion uses raw sensor data before filtering is applied and after applying the calculation table, validation, or expressions specified in the Parameter field of the sensor properties. |
Connectivity and GPS
These criteria are tracked based on the frequency, availability and basic data from the messages sent by the unit device.
| Criterion | Description |
|---|---|
| Distance between messages | Tracks the distance between the coordinates of the two most recent messages. An incident is registered if this distance exceeds the specified value during the selected period. Each new message is compared to the previous one. The default setting is more than 100 km during 1 minute. You can enter only integer numbers. |
| Number of satellites | Tracks the number of satellites used to determine the device location. An incident is registered if the number of satellites is less than the specified during the selected period. The default setting is less than four satellites during 1 hour. |
| Number of messages per hour | Tracks the number of messages received in the last hour (calculated from the current time). An incident is registered if the device sends more than the specified number of messages for the last hour during the selected period. The default value is more than 200 messages per hour during 1 hour. |
| No GPS data | Tracks the coordinates in the device messages. An incident is registered if no coordinates are received during the selected period. The default period is 1 hour. |
| No messages | Tracks whether the device is sending any messages. An incident is registered if no messages are received during the selected period. The default period is 1 day. |