Changes for page 235 - Last Log
Last modified by Carlijn Kokkeler on 2024/12/04 14:02
From version 170.1
edited by Carlijn Kokkeler
on 2023/12/08 09:39
on 2023/12/08 09:39
Change comment:
There is no comment for this version
To version 348.1
edited by Carlijn Kokkeler
on 2024/12/02 11:32
on 2024/12/02 11:32
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 10-DeploymentDelights1 +235 - Last Log - Content
-
... ... @@ -1,24 +1,11 @@ 1 -In th e lastsprint cycle,we focusedonimprovingseveral aspectsrelatedtothedeployments.Itis nowpossibleseeanoverviewof containerversions,andcontainerswill not be deployed andrestartedwhennochangeshavebeenmade. Moreover,severalbugfixes havebeenone relatingtothe Flow Designer,the Deployphase,and alerting.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.2 10-DeploymentDelights||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 -* Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots of the release in the Deploy phase. 8 - 9 -=====Minor changes===== 10 - 11 -* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 12 -* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images. 13 - 14 14 ====Bug fixes==== 15 - 16 -* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 17 -* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. (#1100) 18 -* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 19 -* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck. 20 -* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 21 -* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives. 22 -* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 23 - 24 - 11 +* Deploy - Architecture: The failover container will now be shown correctly.