A core feature of eagle.io is notifications; letting people and teams know that particular alarm thresholds have been crossed (or other significant events have occurred). Several different areas of configuration need to be set up correctly for notifications to work as intended.

1. State configuration

State thresholds are used to trigger state alarms and notifications, but you need to make sure the notification option is actually selected. This is done in the state configuration:

For the above state, notifications have been set to "Active". Note also that the category has been set to "Maintenance".

2. Notification categories and user preferences

Each user profile has a "Notifications" tab allowing a user to select which notifications categories they care about, and how they want to be notified. These settings are configured per Workspace.

In the above example, the user has selected to receive email notifications for the "Maintenance" category, but not SMS notifications. All other categories will result in both an email and an SMS. This means that if our previous state example was to send a notification indicating the "VERY HIGH" threshold had been crossed, this user will only receive an email. That is because the notification category of that state has been set to "Maintenance". In order for this user to receive an SMS for that specific state, either the state category would need to be changed, or the user would need to check the box to receive Maintenance notifications via SMS.


3. Node subscriptions.

Once the state configuration and user notification preferences are set correctly, the final step is for the user to be subscribed to the relevant Node, indicating they care about receiving notifications regarding that specific Node. There are several ways to achieve this, but the simplest is to click the eye icon so that it turns blue. For example, the user is not subscribed to the following Parameter, because the eye is greyed-out:

After clicking the eye, it turns blue, and the user is subscribed to any notifications generated by that Parameter (subject to the previously mentioned category and notification settings):

There are other ways to subscribe; you can use the Workspaces tree menu:

And you can select the checkbox for multiple (or all) Nodes in list view, the use the Notifications button:

4. Managing notifications

Finally, the "Manage notifications" feature is a powerful way of combining several of the previous configuration steps, as well as allowing management on behalf of other users. Access this feature from the Workspaces tree menu:

At the top of the manage notifications window, you can choose which user to manage. Below that is a menu which shows a hierarchy of Nodes next to eye icons; a grey eye means not subscribed, a dark blue eye means subscribed, and a light blue eye means one or more Nodes contained within are subscribed (e.g. a Parameter within a Data Source). On the bottom of the window is a list of which notification categories and methods (email or SMS) have been selected for the current user.

In the above example, I am the currently selected user. Both the Location and Data Source Node have the light blue eye, indicating that some Node below them is subscribed. And the notification categories indicate that this user will receive both email and SMS notifications for all categories (except for "Maintenance" which is only email).

We can expand the Data Source Node to see the exact Parameter that is subscribed; note the "Temp" Parameter has a dark blue eye:

In summary, notifications are a powerful feature but require some thoughtful configuration to achieve the intended results. If you (or your clients) are not receiving the notifications you expect, the above topics make a good troubleshooting checklist to see where the problem lies.


Did this answer your question?