Alerts

Overview

Alerts are based on Events that occur in the system. If defined, an event can lead to an alert being triggered if event is still valid after a defined period of time.

Example:

• System detects an abnormal consumption and create the related Event
• If the abnormal consumption is still detected after 1 minute, an alert is triggered
• As long as the Event is valid, the Alert is maintained
• If the abnormal consumption is below the threshold, the alert is closed.

Every hour, a reminder for pending alerts is sent so that a user can take action and not miss any alerts.

Alert types

Several categories have been set to regroup alerts :

• Water temperature for burning/freezing or bacteriological risks,
• Flowbox Internals for internal metrics (temperature, humidity),
• Abnormal consumption,
• Abnormal consumption with automatic closing enabled,
• Flowbox dysfunction (hardware related issues),
• Flowbox communication : disconnection, connection, etc.
• Maintenance,
• Leakage detection.

Each User can edit his profile and enable/disable the category he wants to be notified about.

Notifications

Notifications can be enabled in the Browser or on Mobile and Tablets. To enable the feature, click on the "Bell" icon in the top right corner of the application and click on "Enable browser notifications". Notifications will show up when the application is active.

Notifications will also be sent by email to Customer Managers and Site Managers who enabled Alerts in their profile.

Platform administrators have also the ability to setup Mattermost or Slack notifications for all alerts.

Silencing vs Resolving an Alert

Silencing an alert will mute the Alert for 24 hours. It will remain visible in the application but it will no longer send alerts nor reminders.

Resolving an alert will close the alert and it will not be visible in the application anymore till it occurs again.