Kio Asset Tracker alerts are activated when assets either enter or exit a specified location. Alerts are activated by Alert Rules that define the monitored locations and assets, and the alert notification recipients. To view and respond to alerts, which are available in the Alert List view, you must be assigned to the Asset Tracker Administrator or User role.
If you are responsible for responding to alerts, the following provides details on how to to respond and manage alerts.
Topics include:
The alert lifecycle represents the various stages, workflow, and statuses that an alert goes through from activation to resolution.
Within Asset Tracker, the state of an alert is identified by its status — New, Acknowledged, and Resolved — providing users with an instant overview of each alert's current state. This structured approach ensures a standard, predictable alert progression workflow, starting from the moment an alert is activated to its resolution.
Alert Stage |
Alert Workflow |
Alert Status |
---|---|---|
Activate |
Conditions set in an Alert Rule is reached > alert is activated. |
New |
Notify |
Notifications are sent to the alert recipients (defined in the Alert Rule) to notify staff of the alerting event. An alert notification includes: (1) the asset (2) time of activation (3) alert name and type of alert (4) location of the alert (campus, building, floor, and room). Alerts with a critical severity level: additional in-app visual and audio alert are activated. |
New |
Acknowledge |
Alert Responder sets the alert to "Acknowledge" to indicate they are taking action. |
Acknowledged |
Resolve |
Alert Responder sets the alert to "Resolve" to indicate the alerting event has been resolved and enters notes related to the event. All alert activity and data is permanently stored in the alert details and activity timeline. |
Resolved |
When you receive an alert notification, you can quickly view the asset's real-time location and acknowledge the alert to indicate that action is being taken. Acknowledging an alert provides other notification recipients with the visibility into the current state of the alerting event. If an alert has already been acknowledged, you can view the alert details and its activity log for additional information.
-
From your Kontakt.io Launchpad, select Asset Tracker.
-
From the left menu, select Alerts List.
-
From the New tab, locate the alert > select its Alert Name to view its details > select Acknowledge.
If an alert has already been acknowledged, it will be available from the Responded tab.
Both email and text alert notifications provide the following details related to an alert:
-
Alert details: A brief description of the nature of the alert, ensuring users understand the urgency or type of incident.
-
URL link: A direct link to view additional information about the alert in the Kio Cloud platform. This allows users to access the system for more context.
-
Acknowledge/Resolve options: Buttons to acknowledge the alert to indicate they are taking action, as well as option to resolve the alert if applicable.
Resolving an alert indicates all necessary actions have been taken and the alerting condition has been resolved. To resolve an alert, it must first be in the Acknowledged status. If applicable, you can acknowledge an alert and then proceed to resolve it.
-
From your Kontakt.io Launchpad, select Asset Tracker.
-
From the left menu, select Alerts List.
-
Locate and select the the alert's Name.
-
From the alert, select Resolve.
-
Select a Resolution Code and optionally enter Notes related to the alerting event > select Resolve.
Notes provided should follow your organization's policies and procedures.
Each alert maintains a detailed profile with a log of all activities. This includes an activity timeline of each status change,notification details, and notes entered by users. From an alert, you can also download an alert incident report.
-
From your Kontakt.io Launchpad, select Asset Tracker.
-
From the left menu, select Alerts List.
-
Assuming the alert has been resolved, select the Resolved tab.
-
From the list, locate the alert > select its Name. Its details are displayed.
Detail |
Description |
---|---|
Severity |
Identifies the severity of the alert. The severity is configured within the Alert Rule that triggered the alert. A rule's severity can be either be Critical, High, Medium, Low, or Info. |
Status |
The current state of the alert. The state of an alert is identified by its status — New, Acknowledged, or Resolved — providing users with an instant overview of each alert's current state. |
Duration |
The duration of an alert is the total time between when the alert is first triggered (activated) and when it is resolved. This duration measures how long the alert remained in an active state, providing a timeline from activation to resolution. |
Opened |
Date and timestamp of when the alert was activated; monitored conditions set in the Alert Rule was reached. |
Assigned to |
The name of the user that created the Alert Rule that activated the alert. |
Affected Location |
The last received location of the asset at the time the alert was activated. |
Rule Condition |
The Alert Rule's location event that activated the alert. The location event is set within the Alert Rule, which can be set to either be when an asset enters or exits a location. |
Resolution Code |
The value selected when a user changed the alert's status to resolved. |
Note |
The value entered by a user when they changed the alert's status to resovled. |
Alert Rule |
The name of the Alert Rule that activated the alert. |
Alert Type |
The Alert Rule type; this value will always be Location Alert. |
Asset |
The asset that triggered the location alerting event, including its assigned tag's 12 character MAC address. |
The Activity Timeline includes each activity and a timestamp of all actions taken during from alert activation to resolution.
-
Each alert status change - when the alert was activated, acknowledged, and resolved.
-
Alert notifications details.
-
Who made a status change and the notes entered during a status change.
-
If the Alert Rule that triggered the alert is configured with a Webhook, includes the Webhook event and its details.