With Device Health, you can get notified when devices need attention. The app has several features including optional mediums for receiving alerts (email or text messages), elective monitoring of devices (specific devices, device types, or devices in a particular location). And it's one place to view device alert activity to get insights into the overall health of your deployed devices.
Important
Device Health currently requires activation by Kontakt.io. To access this new app, please submit a support request to activate Device Health for your organization's Kio Cloud account.
In this article:
Behind the scenes, Kio Cloud is continuously receiving data from your deployed devices and logging and monitoring their online and data activity, which has always been available from Kio Cloud. And with Device Health, staff can get notified when devices are offline resulting in data not being received by Kio Cloud or when device battery levels are low.
The following provides the series of stages than an alert goes through from activation to resolution.
-
Activated. The condition set in an Alert Rule has been reached and a new alert is activated.
-
Notifications. Alert notifications sent to staff, via email and/or text messages. Also, new alerts are displayed in the Kio Cloud alert notification area.
-
Acknowledged. Staff acknowledges the alert as an indicator they are taking action.
-
Resolved. Staff sets alert to Resolved to indicate the alerting condition has returned to normal. The alert ends including reminder notifications.
-
History. Alert details and actions are logged and retained for historical reporting. Alert analytics are represented within the Alert History Dashboard.
Autoresolve. When an alert is active or acknowledged state, If the alerting condition returns to normal the alert is automatically set to Resolved by the system and the alert ends. This can avoid alert fatigue and minimize the need for action during short-term alerting conditions.
To ensure that Device Health only monitors devices that are deployed and in use, the Deployment Status for a device must be set to Deployed. This is in place to avoid alerts for devices that have not been deployed or are no longer in use.
Note
For Kontakt.io Infrastructure devices, including Portal Lights, Portal Beams, and Anchor Beacons, when these device types are assigned to their installation location within Smart Location or during install using the Kio Setup Manager, their Deployment Status is automatically set to Deployed.
To view or update the Deployment Status of a tag, go to Device Management 2.0, select Tags > from the list select the device. The Deployment Status is located in the General tab.
To view or update the Deployment status of a Portal Light, Portal Beam, or Anchor Beacon, go to Device Management 2.0 > select Infrastructure > from the list, select the device. The Deployment Status is located in the General tab. For detailed instructions, see Manage the Deployment Status of your devices.
From the Kio Cloud Launchpad, select Device Health.
|
Alerts > List. A comprehensive record of all alerts. Displays alerts in various stages - including New, Acknowledged, Resolved, and all alert history. This is where staff can also set an alert's status to Acknowledge or Resolved. Dashboards > Alert History. Provides an at-a-glance view of key alert history metrics. Settings > Alert Rules. Alerts Rules define what’s being monitored by each of the three alert types. An alert is activated when a monitored condition set in an Alert Rule has been reached. |
|
Alert Rules provide a simple but effective way to monitor your devices to ensure that everything is working as intended. From an Alert Rule, you will set the Alert Type as detailed below and also how staff are notified (email or text messages).
Monitors and keeps track of Portal Lights' connection to Kio Cloud to ensure they are connecting to the local WiFi network and sending data to Kio Cloud without issues.
This alert is crucial for ensuring the seamless and uninterrupted flow of data between a Portal Light and Kio Cloud, which also includes the data being received from tags and room sensors that are within range of a Portal Light.
The cause of an Offline status is commonly network or power related or that there were no tags or room sensors within range of the Portal Light that resulted in no data being received by Kio Cloud.
|
Locations What locations... |
Condition options Alert is activated... |
|---|---|
|
All locations Specific campus and its buildings Specific building |
When any Portal Light is Offline for a specified amount of time When a specified quantity of Portal Lights are Offline When a specified percentage of Portal Lights are Offline |
Monitors and keeps tracks of devices' Last Seen timestamp. Last Seen timestamp identifies when data for a device was last received by Kio Cloud.
This alert type is useful for keeping track of devices' statuses and ensuring that their data is being received by Kio Cloud regularly.
|
Locations What locations... |
Applies to What Devices... |
Condition options Alert is activated... |
|---|---|---|
|
All locations Specific campus and its buildings Specific building |
All devices Specific device types |
When a device has not been seen for a specified amount of time |
Monitors the battery levels of battery-powered tags and infrastructure devices.
This alert is useful when you want to know when devices' battery life remaining is getting low - allowing a proactive task to schedule a battery or device replacement.
|
Locations What locations... |
Applies to What Devices... |
Condition options Alert is activated... |
|---|---|---|
|
All locations Specific campus and its buildings Specific building |
All devices Specific device types |
When any device has a battery level that falls below a certain percentage When a specified quantity of devices have a battery level that falls below a certain percentage |
The following provides examples of how Device Health Alert Rules can be set up to monitor your deployed devices. This information is intended to provide guidelines to ensure alerts are activated when it matters and to avoid alert fatigue when alerts are activated too often.
|
Use case |
Deployed devices |
Alert Rule setup |
|---|---|---|
|
Portal Beam and Portal Light monitoring for all Occupancy use cases |
100 Portal Beams, 20 Portal Lights per location, multiple locations |
Infrastructure devices:
|
|
Portal Beam and Portal Light monitoring for all Asset tracking use cases including Asset Tags |
100 Portal Beams, 20 Portal Lights, 500 Asset Tags per location, multiple locations |
Infrastructure devices:
Asset Tags:
|
|
Portal Beam and Portal Light Monitoring for all Staff tracking use cases including Badge Holders |
100 Portal Beams, 20 Portal Lights, 500 Badge Holders per location, multiple locations |
Infrastructure devices:
Badge Holders:
|
|
Monitoring Anchor Beacon Infrastructure for Indoor Wayfinding |
1000 Anchor Beacons and 100 Portal Lights per location, multiple locations |
Infrastructure devices:
|
Before you begin, there are a few things you'll need to know to configure an Alert Rule.
-
What type of alert - Portal Light Offline, Low Battery Level, Last Seen? What are the conditions?
-
Do you want alerts for all devices or specific models?
-
Do you want the alert to apply to all locations, a specific campus and its buildings, or a specific building?
-
Who should receive alert notifications? And how do they need to be notified, via email or text, or both?
-
Do you want a reminder notifications to be sent if the alert has not been resolved in a specified amount of time?
Once you know this information, sign in to Kio Cloud. Go to Device Health > select Alert Rules > select Create Alert Rule. You're guided through the setup process. At anytime, you can create, edit, delete, and enable/disable your Alert Rules.
Alert notifications provide the recipients the needed information to take action. And you can add your own custom messages - helpful when you have SOPs that need to be followed when responding to alerts.
Below are examples of a Portal Light Offline alert notification.
You can get insights into an alert’s lifecycle at anytime, including when it was activated, the duration of the alert, and more! When staff acknowledges or resolves an alert, they can log the action taken for visibility and recording keeping purposes.
From each alert, you can:
-
View the device's location; select Show in Smart Location to view from a visual floor plan.
-
View who responded to alerts and their logged action taken.
-
Generate a PDF report for record keeping or sharing with others that do not have access to Kio Cloud.
The Alert History Dashboard provides an at-a-glance view of key resolved alert metrics. From here, you can quickly assess the overall volume and severity of alerts, as well as trends and patterns over time.
-
Average number of alerts per day: a daily average of the total number of alerts generated, allowing users to quickly understand the overall volume of alerts and track changes over time.
-
Average time to acknowledge: average time it takes for an alert to be acknowledged by the user or system, helping users to assess their response times and identify areas for improvement.
-
Average alert duration: average duration of alerts from creation to resolution, helping users to understand the typical lifespan of alerts and identify trends that may require attention.
-
Number of alerts by alert type: number of alerts generated by each alert type, allowing users to quickly identify which types of alerts are most common and may require additional attention.
-
Number of alerts by location: number of alerts generated by location, helping users to understand where alerts are most frequent and where resources may need to be allocated.
-
Response time by time of the day: average response time for alerts during different times of the day, helping users to identify patterns and trends in their alert response times.