Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 739.1
edited by Carlijn Kokkeler
on 2024/10/09 10:26
Change comment: There is no comment for this version
To version 794.1
edited by Carlijn Kokkeler
on 2024/11/18 14:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -231 - Microscopic Madness
1 +234 - Alert Adventures
Content
... ... @@ -3,37 +3,50 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** The past few weeks we have improved the search options for flow testing logs and monitoring logs. Next to this, we fixed the unused properties overview and improved the deletion functionality of router containers.
6 +**Hi there, eMagiz developers!** In this release, our new error alerting will be available! Please find out more about it here (LINK). Apart from this, .
7 7  
8 -{{warning}}Please note that during this deployment, models on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture will display logs indicating that a connection loss has occurred and attempts are being made to re-establish the connection. This will occur for a period of 15 to 30 minutes sometime during our deployment window. {{/warning}}
9 -
10 10  == **Feedback Items** ==
11 -//__Log search options__//
12 -Search options for flow testing logs and monitoring logs have been improved:
13 -* You can now search for 'logger' and 'message' in both screens.
14 -* The options to search for 'timestamp from' and 'timestamp to' have been removed from flow testing logs.
15 -* The Level is now shown more clearly.
16 -
17 -[[image:Main.Images.Release Blog.WebHome@release-231-manage-log-entries.png]]
9 +//__Error alerting__//
10 +Alerting for message queues 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"]] a couple of 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.
18 18  
12 +{{info}}Please take into consideration the following migration actions:
13 +* 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.
14 +* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
15 +** The 'Description' field has been replaced by the new 'Instructions' field (note: the 'Description' field no longer exists).
16 +** The values of the old description field will be transferred into the instructions field
17 +* 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.
18 +** This field will be automatically populated with a default name (e.g., "Error Trigger 1").
19 +** **Users are advised to review and update these names to appropriately reflect each trigger's purpose**.
20 +* 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:
21 +** "Check header" is disabled.
22 +** "Check error message" is enabled.
23 +** The "Error message contains" field includes only a single character.
24 +* 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}}
19 19  
26 +{{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}}
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-231-flowtest-logs.png]]
28 +{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}
22 22  
30 +//__Attribute selection__//
31 +When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted.
32 +
33 +[[image:Main.Images.Release Blog.WebHome@release-234-cdm.png]]
34 +
35 +//__Attribute selection__//
36 +We have removed some deprecated components from our runtime image:
37 +* TCP support object 'Byte array text length header (de)serializer'
38 +* Mikrotik service activator
39 +
40 +Please find out more [[here>>doc:Main.eMagiz Academy.Release Information.Runtime Images.V320||target="blank"]].
41 +
23 23  == **Bug Fixes** ==
24 -//__Unused properties__//
25 -We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview.
26 26  
27 -//__Router deletion__//
28 -Router containers for failover that were deleted from the Deploy Architecture, are now cleaned up completely from the environment.
29 29  
30 30  == **Fancy Forum Answers** ==
31 31  
32 32  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:
33 33  
34 -* [[SOAP Webservice error when using namespaces>>https://my.emagiz.com/p/question/172825635703978319||target="blank"]]
35 -* [[Unable to retrieve topics in Kafka Mendix module>>https://my.emagiz.com/p/question/172825635703978127||target="blank"]]
36 -* [[application/x-www-form-urlencoded token>>https://my.emagiz.com/p/question/172825635703965691||target="blank"]]
49 +* [[JSON-TO-JSON java.lang.NumberFormatException in string field>>https://my.emagiz.com/p/question/172825635703991104||target="blank"]]
37 37  
38 38  == **Key Takeaways** ==
39 39  
... ... @@ -43,7 +43,7 @@
43 43  * If you have feedback or ideas for us, talk to the Platypus
44 44  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
45 45  * Clear your browser cache (Ctrl + Shift + Del)
46 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.231 - Microscopic Madness.WebHome||target="blank"]]
59 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.233 - Policy Polish.WebHome||target="blank"]]
47 47  * Start thinking about how the license tracker can aid your development
48 48  * Start thinking about major, minor, and patch
49 49  * Keep making great integrations