Trigger Page

A Trigger can be created to take actions when certain events happen or the site is in a particular state. An example of such a trigger could be: “Send me an email when any asset enters a zone” or “Create an Alert for assets with an average connectivity below 95%”.

The Triggers Page shows all of the site's active and inactive triggers, sorted by priority. It also contains the New Trigger Button, for creating new Triggers.

Each trigger is represented by a row. Clicking anywhere on the row (except on one of the action buttons) will open the trigger's editor panel.

If a trigger is Inactive (not currently running) the entire row will be greyed out.

Trigger rows can be dragged to different priority columns to change the trigger's priority.

Using the trigger action buttons you can Duplicate (which opens a new trigger editor with a copy of the original) or Delete the trigger.

Managing Alerted Triggers

When triggers breach their threshold they enter the alerting state. This will colour the trigger status bar red and offer some extra buttons to manage the alerted trigger.

There are extra actions that you can perform to an alerting Trigger:

  • Silence - Will allow a user to silence the alert for a period of time.
  • Resolve/Close - Resolving/Closing an alert will allow subsequent trigger threshold breach events to show up as a new alert notification.

Silencing An Alerting Trigger

Silencing an alerting Trigger is the ability to silence an alert for an specific amount of time, during this time it will no longer notify. Once the snooze time is reached, notifications will re-commence. Once clicking snooze trigger button it will show some pertinent information:

  • Indefinitely - Silenced forever
  • Later today - Silence for 1 hour
  • Tomorrow - Silence for 24 hours
  • Next week - Silence for 7 days
  • Custom Snooze - Allows you to select the date / time you want the alert to remain silenced to.

Trigger Creation

To create a new trigger, hover over the New Trigger Button and select a trigger type from the buttons that appear above.

Trigger Editor

Details Tab

This is where you can set the name, description and priority for the trigger.

Query Tab

A Trigger can be created to take actions when certain events happen or the site is in a particular state. An example of such a trigger could be: “Send me an email when any asset enters a zone” or “Create an Alert for assets with an average connectivity below 95%”.

Triggers are completely customizable and can target many parts of the system meaning there are a few components to creating one. The first choice when making a new Trigger is the Type. Currently there are 2 types of trigger, Count and Aggregation. The best way to explain the difference between the 2 types is by examples. In general count triggers are for events, whereas aggregation triggers are for aggregating statistics.

  1. Count Trigger Examples
    • Alert if an asset enters a zone.
    • Alert if an asset changed state from Happy to Sad
  2. Aggregation Trigger Examples
    • Alert if the average connectivity of an asset is below 95%
    • Alert if the maximum latency of an IP device is greater than 100ms

The next two components are the Time Frame and Grouping

  1. Time Frame
    • Denotes how much data the trigger should aggregate each time it checks the system. We can elaborate on the example trigger to include time frame in it’s description: “Create an Alert for assets with an average connectivity below 95% in the last 5 minutes”. Where 5 minutes is the selected time frame of the Trigger. All triggers must have a timeframe.
  2. Grouping
    • Defines what the Trigger is targeting. In the example Trigger, the grouping would be Asset. So we could use the grouping to target each asset separately, each IP Device or even the entire Site; for example “Create an alert if the average connectivity for the Site is below 95%”.

Combining Time Frame and Grouping already allows for many different triggers through their combinations.

  • Alert if the Site’s average connectivity is low for the day
  • Alert if an Asset Type’s average connectivity is low over a 5 minute period

The next two components of triggers the Filters and Conditions

  1. Filters
    • Filters out any data for being triggered on. To elaborate on the example again adding a filter might look like: “Alert if any Dump Truck has a connectivity before 95%”. To achieve a trigger like this the grouping would have to be Asset and then a filter applied for the Dump Truck Asset Type.
    • Filters can be used to target very specific pieces of data. A more complicated example might be “Alert if an asset who is a Excavator and belongs to Site 1, or is a Dump Truck and belongs to Site 2”. This would require 4 filters.
  2. Conditions
    • Conditions generally make up the main statement of the trigger, as bolded in the example “Alert if an asset has an average connectivity less than 95% over 5 minutes”.
    • Like filters, conditions can be combined and nested to form more complicated logic. An example of this might be “Alert if an asset has low connectivity OR (high latency AND moderate connectivity)”.

Below are some example triggers and what they would look like in the Trigger Editor

Alert if more than 2 Assets on Mine Site 1 enters Zone A in the last 5 minutes.

Alert if any IP Device with a Tag of Backhaul and Asset Type of Trailer has a average latency less than 100ms and a maximum latency less than 200ms and it's between 12pm and 1pm .

Actions Tab

Actions are the things that happen once a trigger’s conditions are met. It should be noted that an Alert is currently always created for a Trigger when it trips and is updated upon subsequent trips, if the Alert is closed a new Alert will be created once the Trigger trips again. Visit the Alert wiki page for more information on this. Actions of the trigger such as sending emails only happen once an Alert is created. Any number of actions can be added to each alert.

The example below shows an email that will be sent when the trigger trips. It will also include the data from the trigger similar to that data in the alert.

Alert History Tab

The Alert History allows the user to browse the past runs of a trigger. The horizontal time bar in the alert history overview highlights failures over the past week. The vertically browsable list shows the trigger run results from the past hour. Both of these visualisations are tied to the application's current time. To browse to different times use the date / time selector in the centre panel.

You may want to create an incident to track the trigger from this tab. The ticket will be created at the trigger's threshold breach time stamp.

Activity Tab

Shows the activities for the trigger.

Comments Tab

The comments tab provides a way to view and add comments, filtered to this trigger.