It’s nice and fun to see your data coming in, but you are probably not looking at your screen 24/7 to monitor and take action when needed. This is where a set of powerful functionalities of the platform come into play: event triggers, events and notifications. In short, event triggers are used to define rules on a metric that eventually will lead to an event and possible notifications.
Using event triggers
Event triggers are used to specify your rules on metrics. This assures you to get an event when a real-time measurements of that metric is violating your rule. The configuration of a trigger is of crucial importance since this will lead to events that you will act on. Make sure you give it a recognizable name (1), connect it with the right metric (2), link to one or more subjects (3) and set the event rules (4). You will see a green arrow (5) when occurrence and/or time constraints are added to a rule.
Managing event triggers
Event triggers and its rules are flexible to make it useful in many circumstances. Here you find the actions and configuration information.
Creating event triggers
|Name||Give your trigger a descriptive name so you can easily recognize and find it.|
|Metric||Choose for what metric you want to configure the trigger.|
|Subjects||Select the subjects this event trigger applies to.|
|Event rules||Add event rules to define the conditions will lead to an event.|
Configuring event rules
You can see the levels of priority when configuring the rules of a trigger. Just so you know, you do not need to set every level. For example, an metric can move from Problem to OK, depending on how you configured the rules. Here is the information about the levels:
|OK||(no action needed)||Green|
In addition, you can set several occurrence and/or time constraints on your event rules. Please see the screenshot above for an example and see the video below for the configuration.
Here you can see a Blockbaxer creating an event trigger based on the following requirements
- I want to be informed when the temperature is higher than 22 degrees,
- I want to be warned when the temperature is above 23 degrees and
- I want to see a problem coming in when the temperature is above 24 degrees for longer than 30 minutes when the office is open (Mo-Fr from 08:00 - 17:30).
Editing and deleting event triggers
Editing and deleting event triggers can be tricky. Associated events of the trigger will be removed and future events based on the event rules of the trigger are not generated anymore. So, please be careful. This where you can edit and delete an event trigger:
Events are your friend, because they help you to understand what is happening so you can take the action that is needed. In the events overview page, you can filter on subject, metrics, event triggers and properties (1), so you can make a cross section of the events you like to see. In addition, you can filter on the status of an event (2) or within in a certain time-window (3). You can use the arrows (4) to jump to different time-windows and the pause button (4) to (un)freeze your current stream of events. The first of the buttons (5) can be toggled to see grouped events and the second is to show active events. Grouped events are grouped by the number of times they occurred based on the selected period and active events are still running (red. events without end date) events. The list of events (6) is constrained on the filters you have applied.
Showing event details
The event details are shown when clicking on one of the events in the overview page (see previous section). Here you can see some details (1) and when the event occurred (2). It is possible to zoom-in on the event by selecting an area on the graph (3).
Here you can see a Blockbaxer navigating through the events including zooming in on an particular event
Notification are used to get updates within the platform, via e-mail and/or SMS. The platform notifications are visible by clicking on the bell in the top-right corner of your screen (1). Once opened you can navigate to the notification settings (2), only show the unread notifications (3), mark all your notifications as read (4) or click on a notification to directly navigate to the event (5).
The default settings can be applied level-wide (1). For example, you can quickly enable notifications for all Problem events or start to receive weekly-digests. If needed, you can overwrite the default settings by using custom settings per metric per event level (2). Optionally, you can also receive notifications via e-mail and/or SMS.