Alerts

Alerts

Clicking on Inbox, will show you any unattended alerts, note that this module updates in real-time, so there’s no need to refresh, the alerts will come in and update automatically.

🚧

Alert History

Alerts are stored in the gateway for the past month and the current month. After 2 months the alerts are erased and cannot be recovered.

📘

Working with SLAs

It's important that when working with SLAs you use the Grouping "None" option so you can see the individual SLA for each alert fired.

Alert Options

To mark an alert as attended, you can either click on the checkmark icon next to the alert's name, or open the alert by clicking on its name, and then click on the RESOLVE button at the bottom. Once resolved, the alert must be reopened to modify any option. Note that Critical alerts require a comment before marking them as resolved.

The alert dialog shows information like:

• Event date: the date the event occurs
• Alert date: the date the alert occurs
• Vehicle: vehicle assigned to the trigger. For more information see Automation/ Triggers
• Asset: asset assigned to the trigger. If the alert has no driver assigned, the user can assign an asset to the alert. This association will be only between the alerts and the driver.
• Mark as a false positive: If the user wants to cancel the alert.
• The alert dialog displays the Hour of Services of the entity at the moment the trigger fired, for example, if the entity is Working or Resting, how long the entity has been working continuously, and if the cycle is valid or not.
• Due date: only appears for alerts with SLA. Shows the deadline to resolve the alert.
• The share icon allows you to share events via email

Mark as a false positive

• Once clicked on this option a comment is required and the entered text will be reflected as a message in the comments. The Alert will be "Canceled" unless the user Resolves it.

• The user can uncheck this option if the alert is not a false positive

Resolution options

• RE-OPEN: displayed for attended alerts.
• RESOLVED: displayed for unattended, canceled alerts.
• RECEIVED / READ ACK: when the alert has the option "Require a read receipt", which means that the user that receives the alert will have to click a button that they 'read' the message before resolving it. This is helpful when multiple users receive the alert and you want to know which one is working on it before they resolve it. More info in Automaton / Triggers.

Grouping alerts and SLA

Entity: Groups triggers by the entity.

Entity/Trigger: The entity is grouped according to its triggers.

Entity/SLA: Group the triggers with SLA. For example, the vehicle "TBZ39D" with the trigger "Alert Warning with SLA" will group all the alerts with SLA, and the same vehicle with the trigger "Vehicle started overworking" that does not have SLA will group the alerts without SLA.

None: grouping is not applied. This is the best view to display the SLA alerts.

The alert with SLA will have two states:

• NEW: the alert is unresolved
• DELAYED: the alert that has not been attended before the time established in the SLA, example: if the SLA is 2h and the alert has not been resolved before this time, the alert will be delayed

The "Canceled" alerts will be false positives.

Once you’ve attended several alerts you can click the following button to clear them:

Notifications

Notifications are custom messages that can be generated for other users on a specific schedule. The notifications can have rich text including attachments like images or documents.

To get started click on the "Create New Notification" button, next to the Notifications section, type in the message, and hit SAVE.

Once a notification is SAVED the user will receive it and get a popup message on the top right corner.