User Tools

Site Tools


alerts

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
alerts [2018/08/06 08:37] emozolyakalerts [2020/04/08 15:28] – [New alerts configuration] emozolyak
Line 1: Line 1:
 ====== Alerts ====== ====== Alerts ======
  
-----+===== New alerts configuration =====
  
 +In WebHMI there is the concept of an alert. An alert is a state of the system that requires human attention. WebHMI signals on all alerts visually (red status bar on the dashboards) and an audible signal about unqualified accidents. The alerts are kept in a special alerts log. 
 +
 +Starting from 3.6 fw version, __a new alert setup__ has beed implemented. For versions below 3.6 please refer to the next section. 
 +
 +When some alert triggers there will be pop-up window, like this - 
 +
 +{{ ::descent_alert_msg2.png?direct&400 |}}
 +
 +There will be the alert title, group (if it belongs to a group), start time, duration, acknowledge status and the link to details. 
 +In the new alerts there is a number of improvements:
 +  *more complex conditions for each alert. 
 +  *richer alert description with insructions  (extended text format, pictures)
 +  *operator can add comments after alert has been triggered
 +  *templates - for identical devices with the same alerts conditions, you can setup only one template 
 +
 +The alert setup link is here:
 +
 +{{ ::alerts_link.png?direct&400 |}}
 +
 +The example of an alert list:
 +
 +{{ ::new_alerts_list_commented.png?direct&400 |}}
 +
 +Here:
 +  -is the button to create an **alert object**
 +  -is the button to create an **alert group**
 +  -is the list of non-grouped alerts
 +  -is the **category** name for organizing the list. There are 2 groups in the example provided. 
 +  -it is a list of **grouped alerts**. The titles in bold text indicate group title. Only a group can be a template for another group of alerts. The template column tells if the group is a template or templates' descendant. 
 +  -is a list of **templates' descendants**. For descent alert groups you can tell the system substitution rules for the registers, in the same way as for dashboard templates.
 +
 +In the __Basic__ edit alert tab you set title, template, category and level (Info, Warning, Alert), wether to allow acknoledge and sound signal.
 +
 +{{ ::alert-edit-basic-tab.png?direct&400 |}}
 +
 +In the __Condition__ tab, you define the condition which will trigger the alert. It can be specific bit of a register or its value (=, ≠, <, >, [a, b]((in range from a to b))). The multiple conditions are combined only with AND operator. So for OR operation or more complex conditions you can use Lua scripts. 
 +
 +{{ ::alert-edit-contition.png?direct&400 |}}
 +
 +In the __Information__ tab, there is a text editor with formatting options to create messages including one optional picture. This message will be shown if an operator press Details... link in the alert pop-up dialog. 
 +
 +{{ ::alert-edit-information.png?direct&400 |}}
 +
 +Information page in this case could be like this:
 +
 +{{ :alerts.png?direct&400 |}}
 +
 +All alerts are stored in their log, which can be accessed from side bar or context menu link.
 +
 +{{ ::new_alert_log_view.png?direct&400 |}}
 +
 +
 +
 +
 +
 +
 +
 +
 +
 +===== Alerts configuration before 3.6 fw version =====
  
 In WebHMI there is the concept of an alert. An alert is a state of the system that requires human attention. WebHMI signals all alert visually (red status bar on the dashboards) and an audible signal about unqualified accidents. Emergencies are logged for later analysis. In WebHMI there is the concept of an alert. An alert is a state of the system that requires human attention. WebHMI signals all alert visually (red status bar on the dashboards) and an audible signal about unqualified accidents. Emergencies are logged for later analysis.
alerts.txt · Last modified: 2022/10/10 08:46 by emozolyak

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki