Skip to Content

Changes for page 235 - Last Log

Last modified by Carlijn Kokkeler on 2024/12/04 14:02
From version 173.1
edited by Carlijn Kokkeler
on 2023/12/21 16:12
Change comment: There is no comment for this version
To version 348.1
edited by Carlijn Kokkeler
on 2024/12/02 11:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +235 - Last Log
Content
... ... @@ -1,19 +1,11 @@
1 -In the last sprint cycle, we focused on improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.
1 +In this release, our new log alerting will be available! Please find out more about it **LINK**. Furthermore, we have implemented improvements for SMB and did some performance improvements. Lastly, from now on we no longer support our legacy Mendix connector (< version 4.x).
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.235 - Last Log||target="blank"]].
4 4  
5 -=====New features=====
5 +====Minor changes====
6 +* Manage - Alerting: 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. Please check out our [[release blog>>Main.Release Information.Release Blogs.235 - Last Log||target="blank"]] for the migration actions, and our new **ML LINK** about the design.
7 +* Design - CDM: When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted. (#1150)
8 +* Deploy - Deployment: We have removed some deprecated components from our runtime image. Please find out more [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]].
6 6  
7 -
8 -
9 -=====Minor changes=====
10 -
11 -* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
12 -
13 -
14 -
15 15  ====Bug fixes====
16 -
17 -
18 -
19 -
11 +* Deploy - Architecture: The failover container will now be shown correctly.