Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 818.2
edited by Carlijn Kokkeler
on 2024/12/02 10:08
Change comment: Update document after refactoring.
To version 820.1
edited by Carlijn Kokkeler
on 2024/12/02 10:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,8 +9,22 @@
9 9  
10 10  == **Feedback Items** ==
11 11  //__Log alerting__//
12 -We have added log message alert triggers to our new alerting stack for the current runtime architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well.
12 +We have added log message alert triggers to our new alerting stack for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well.
13 13  
14 +{{info}}
15 +* **Please take into consideration the following migration actions**:
16 +* All existing log message alert triggers from the current generation (Gen3) models will be automatically migrated to the new alerting feature.
17 +* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
18 +** The ‘Description’ field has been replaced by the new ‘Instructions’ field (note: the 'Description' field no longer exists).
19 +** The values of the old description field will be transferred into the instructions field
20 +* Additionally, a new field, ‘Name’, has been introduced for identification purposes. The ‘Name’ field will be included in email notifications when a trigger is activated.
21 +** This field will be automatically populated with a default name (e.g., "Log Trigger 1").
22 +** Users are advised to review and update these names to appropriately reflect each trigger's purpose.
23 +* A new filter for ‘Log level’ has also been added to the new Log alert triggers, which will be configured such that your existing triggers will generate an alert for all log types.
24 +* The new feature introduces duplicate detection when saving an individual log trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate log alerts.
25 +{{/info}}
26 +
27 +
14 14  == **Bug Fixes** ==
15 15  
16 16