Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 824.1
edited by Carlijn Kokkeler
on 2024/12/02 10:20
Change comment: There is no comment for this version
To version 740.1
edited by Carlijn Kokkeler
on 2024/10/10 08:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -235 - Last Log
1 +231 - Microscopic Madness
Content
... ... @@ -3,37 +3,35 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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.
7 7  
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 -
10 10  == **Feedback Items** ==
11 -//__Log alerting__//
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.
9 +//__Log search options__//
10 +Search options for flow testing logs and monitoring logs have been improved:
11 +* You can now search for 'logger' and 'message' in both screens.
12 +* The options to search for 'timestamp from' and 'timestamp to' have been removed from flow testing logs.
13 +* The Level is now shown more clearly.
14 +
15 +[[image:Main.Images.Release Blog.WebHome@release-231-manage-log-entries.png]]
13 13  
14 -{{info}}
15 -* **Please take into consideration the following migration actions**:
16 -* All existing log 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., "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 26  
27 -{{warning}}Please check out our **LINK** for an elaborate explanation of our new error alerting. {{/warning}}
28 28  
19 +[[image:Main.Images.Release Blog.WebHome@release-231-flowtest-logs.png]]
20 +
29 29  == **Bug Fixes** ==
22 +//__Unused properties__//
23 +We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview.
30 30  
25 +//__Router deletion__//
26 +Router containers for failover that were deleted from the Deploy Architecture, are now cleaned up completely from the environment.
31 31  
32 32  == **Fancy Forum Answers** ==
33 33  
34 34  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:
35 35  
36 -* [[H2 database following a queue channel without message store>>https://my.emagiz.com/p/question/172825635704003822||target="blank"]]
32 +* [[SOAP Webservice error when using namespaces>>https://my.emagiz.com/p/question/172825635703978319||target="blank"]]
33 +* [[Unable to retrieve topics in Kafka Mendix module>>https://my.emagiz.com/p/question/172825635703978127||target="blank"]]
34 +* [[application/x-www-form-urlencoded token>>https://my.emagiz.com/p/question/172825635703965691||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.234 - Alert Adventures.WebHome||target="blank"]]
44 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.231 - Microscopic Madness.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