Alert Rules provide a simple but effective way to monitor your Kontakt.io 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 when an alert is activate.
Topics include:
The Portal Light Offline alert rule monitors and keeps track of Portal Lights' connection to Kio Cloud - to ensure they're 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 Portal Lights and Kio Cloud, which also includes the data received from Kontakt.io BLE-only devices that are within range of Portal Lights.
The cause of an Offline status is commonly network or power related or that there were no BLE-only devices within range of a Portal Light that resulted in no data being received by Kio Cloud.
The following is required when creating a Portal Light Offline Alert Rule.
|
Setting |
Information required |
|---|---|
|
General |
Alert Name: uniquely identifies the rule. Alert Severity: Critical (in addition to notifications, emits an audio alert within Kio Cloud), High, Medium, Low, info Activate Alert Rule after saving: By default, this option is selected and rule is set to a status of enabled to actively monitor the condition. To disable the alert, deselect Activate Alert Rule after saving. You can always enable the alert at a later time. |
|
Locations |
The options include:
|
|
Conditions |
When the condition is reached, an alert is activated. The options include:
|
|
Actions |
Set how and who is notified when an alert is activated. The options include:
Alert Reminder: For those mission critical devices, you have the option to enable alert notifications to be sent again in the event that an alert is not advanced to resolved within a designated window of time (days, hours, or minutes). |
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.
The following is required when creating a Last Seen Alert Rule.
|
Setting |
Information required |
|---|---|
|
General |
Alert Name: uniquely identifies the rule. Alert Severity: Critical (in addition to notifications, emits an audio alert within Kio Cloud), High, Medium, Low, info Alert Severity: identifies the severity of alerts activate by the rule; options include Critical, High, Medium, Low, Info. Activate Alert Rule after saving: By default, this option is selected and rule is set to a status of enabled to actively monitor the condition. To disable the alert, deselect Activate Alert Rule after saving. You can always enable the alert at a later time. |
|
Applies to |
Sets what devices are monitored by the rule. The options include:
|
|
Locations |
The options include:
|
|
Conditions |
When the condition is reached, an alert is activated. The options include:
|
|
Actions |
Set how and who is notified when an alert is activated. The options include:
|
Monitors the battery levels of battery-powered BLE-only 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.
The following is required when creating a Low Battery Alert Rule.
|
Setting |
Information required |
|---|---|
|
General |
Alert Name: uniquely identifies the rule. Alert Severity: Critical (in addition to notifications, emits an audio alert within Kio Cloud), High, Medium, Low, info Activate Alert Rule after saving: By default, this option is selected and rule is set to a status of enabled to actively monitor the condition. To disable the alert, deselect Activate Alert Rule after saving. You can always enable the alert at a later time. |
|
Locations |
The options include:
|
|
Applies to |
Sets what devices are monitored by the rule. The options include:
|
|
Conditions |
When the condition is reached, an alert is activated. The options include:
|
|
Actions |
Set how and who is notified when an alert is activated. The options include:
Webhooks: sends alerts to an external system by a Webhook created and managed within Company Settings. Alert Reminder: For those mission critical devices, you have the option to enable alert notifications to be sent again in the event that an alert is not advanced to resolved within a designated window of time (days, hours, or minutes). |
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 |
|---|---|---|
|
Workspace Occupancy Floor footfall traffic, seat-level occupancy, room occupancy, environmental monitoring |
100 Portal Beams, 20 Portal Lights per location, multiple locations |
Infrastructure devices:
|
|
Medical Equipment Management; RTLS solutions |
100 Portal Beams or Beam Minis, 20 Portal Lights, 500 Asset Tags per location, multiple locations |
Infrastructure devices:
Asset Tags:
|
|
Staff Safety & Staff Journey Analytics |
100 Portal Beams or Beam Minis, 20 Portal Lights, 500 Badge Holders per location, multiple locations |
Infrastructure devices:
Badge Holders (Smart Badges):
|
|
Indoor Navigation |
1000 Anchor Beacons and 100 Portal Lights per location, multiple locations |
Infrastructure devices:
|