Alerts

The Alerts module allows users to monitor alerts and manage notification policies.

In Enelyzer, there are two types of alerts:

No Data Alerts

• Monitor automatic data ingestion flows (e.g., Fluvius API, MQTT messages).

• In the current beta version, it is not yet possible for users to create their own No Data alerts on integrations. If you would like to monitor an automatic data ingestion flow, please contact [email protected].

Operational Alerts

• Check whether specific conditions are met.

• These alerts can be fully created and managed by users.

• Enelyzer discriminates between:

  • Running Value Alerts

    • Monitor aggregated or accumulated values over a defined period.

    • Example: alert if the daily electricity consumption of a facility exceeds 500 kWh.

  • Instant Alerts

    • The system checks the most recent value within a time window equal to twice the logging interval.

    • Example: alert if the temperature at a given moment falls below 18°C.

• Both types can be configured with custom conditions and linked to notification policies, so that the responsible users receive alerts in the defined period.

Creating an Operational Alert

Instant Alerts

• Condition – one condition referring to at least one tag. For instant alerts, the condition is always evaluated using the normalised data of the tag(s).

• Name and description – to clearly identify the alert.

• Threshold period – the period during which the condition must be met to trigger the alert.

• Severity level – specify whether the alert is an Alarm, Notification, or Informational.

• Contacts – choose who should receive the alert:

  • One or more contact groups (can include non-Enelyzer users), or

  • A single contact person (must be an Enelyzer user).

After the creation of the alert, you can:

• Edit – alerts can be modified at any time.

• Pause – alerts can be temporarily paused if needed.

• Update notification settings

  • Edit the contacts

  • Set quiet times - to prevent alert notifications during defined periods.

• Delete - alerts can be deleted at any time.

Running Value Alerts

• Condition – one condition monitoring on ore more tags, each with their own selected unit.

• Name and description – to clearly identify the alert.

• Threshold period – the period during which the condition must be met to trigger the alert.

• Severity level – specify whether the alert is an Alarm, Notification, or Informational.

• Contacts – choose who should receive the alert:

  • One or more contact groups (can include non-Enelyzer users), or

  • A single contact person (must be an Enelyzer user).

After the creation of the alert, you can:

• Edit – alerts can be modified at any time.

• Pause – alerts can be temporarily paused if needed.

• Update notification settings

  • Edit the contacts

  • Set quiet times - to prevent alert notifications during defined periods.

• Delete - alerts can be deleted at any time.

Alert Overview

In the Alerts Module, you can view the list of all existing alerts for your organisation, divided into Operational Alerts and No Data Alerts.

Filtering and status:

• Alerts can be filtered by firing status, severity, assigned contact groups, or associated tags.

• Firing alerts are shown at the top of the list.

• A red bell icon indicates alerts that are currently firing and displays the number of tags causing the firing status.

Viewing alert details:

• Click on an alert to open its details page and review its configuration, conditions, and notification policies.