Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 816.1
edited by Carlijn Kokkeler
on 2024/12/02 09:51
Change comment: There is no comment for this version
To version 818.1
edited by Carlijn Kokkeler
on 2024/12/02 10:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,49 +8,12 @@
8 8  {{info}}Please note that this is our last release of the year. Our next release will be on the 16th of January!{{/info}}
9 9  
10 10  == **Feedback Items** ==
11 -//__Error alerting__//
12 -Error alerting has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, following our queue alerting design that has been [[released>>doc:Main.Release Information.Release Blogs.226 - Alerting Alchemy.WebHome||target="blank"]] several months ago. The new error alerting feature allows you to trigger an alert on **all** incoming errors, or choose to trigger when **specific filters** on the error’s headers, message or class have been met. Furthermore, you can select the specific runtime the error originated from as one of the filters as well.
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.
13 13  
14 -{{info}}
15 -Please take into consideration the following migration actions:
16 -* All existing error message alert triggers from the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture 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., "Error Trigger 1").
22 -** **Users are advised to review and update these names to appropriately reflect each trigger's purpose**.
23 -* If an error message alert trigger has the following specific configuration, its trigger conditions will be migrated such that alerts are triggered for **all** incoming error messages:
24 -** "Check header" is disabled.
25 -** "Check error message" is enabled.
26 -** The "Error message contains" field includes only a single character.
27 -* The new feature introduces duplicate detection when saving an individual error trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate error alerts.{{/info}}
28 -
29 -{{warning}}To keep a better overview, we recommend you to remove your old dynamic triggers after the new error triggers are activated, these have already been disabled by our migration process. The same applies for your queue-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page.{{/warning}}
30 -
31 -{{warning}}Please check out our [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-error-alerting.WebHome||target="blank"]] for an elaborate explanation of our new error alerting. {{/warning}}
32 -
33 -//__Attribute selection__//
34 -When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted.
35 -
36 -[[image:Main.Images.Release Blog.WebHome@release-234-cdm.png]]
37 -
38 -//__Runtime image__//
39 -We have removed some deprecated components from our runtime image.
40 -* TCP support object 'Byte array text length header (de)serializer'
41 -* Mikrotik service activator
42 -
43 -Please find out more [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]].
44 -
45 -{{warning}}We recommend evaluating custom groovy scripts and SpEL expressions to ensure that they do not rely on functionality that may have been removed due to one of the library removals.
46 -* Calls to com.emagiz.util.Assert can be replaced with org.springframework.util.Assert
47 -* Calls to com.emagiz.util.StringUtils can be replaced with org.springframework.util.StringUtils
48 -* Calls to com.emagiz.util.CollectionUtils can be replaced with org.springframework.util.CollectionUtils{{/warning}}
49 -
50 50  == **Bug Fixes** ==
51 -//__Failover container__//
52 -The failover container will now be shown correctly.
53 53  
16 +
54 54  == **Fancy Forum Answers** ==
55 55  
56 56  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: