alerts
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
alerts [2020/04/08 14:44] – [New alerts configuration] emozolyak | alerts [2022/01/13 13:22] – [New alerts configuration] emozolyak | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{ :: | ||
====== Alerts ====== | ====== Alerts ====== | ||
Line 7: | Line 8: | ||
Starting from 3.6 fw version, __a new alert setup__ has beed implemented. For versions below 3.6 please refer to the next section. | 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 - | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | 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: | In the new alerts there is a number of improvements: | ||
*more complex conditions for each alert. | *more complex conditions for each alert. | ||
Line 33: | Line 39: | ||
{{ :: | {{ :: | ||
- | 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]((1))). The multiple conditions are combined only with AND operator. So for OR operation or more complex conditions you can use Lua scripts. | + | 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. |
{{ :: | {{ :: | ||
+ | |||
+ | 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. | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | Information page in this case could be like this: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | All alerts are stored in their log, which can be accessed from side bar or context menu link.The following filters are available for convinient looking-through: | ||
+ | * Level - info, warning, alert | ||
+ | * title - with find sub-string | ||
+ | * group | ||
+ | * status - active / fixed, acknoledged and not acknowledged | ||
+ | Every column has a sorting action and an omni-search box is provided as well to search in all alerts. | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | <wrap em>As of 4.0 fw version there is an alert comment dictionary </ | ||
+ | I.e. an operator can quickly select on of the predefined messages to comment the alert or his action, etc. | ||
+ | There is a field to select the dictionary for this: | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | Then when acknowleding or viewing the alert, an operator can quickly select the desired dictionary entry. | ||
+ | |||
+ | {{ :: | ||
+ | |||
+ | |||
alerts.txt · Last modified: 2022/10/10 08:46 by emozolyak