Changes for page 235 - Last Log
Last modified by CarlijnKokkeler on 2024/12/04 14:02
From version 348.1
edited by CarlijnKokkeler
on 2024/12/02 11:32
on 2024/12/02 11:32
Change comment:
There is no comment for this version
To version 103.1
edited by Erik Bakker
on 2023/08/29 11:07
on 2023/08/29 11:07
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 35-Last Log1 +204 - Found It - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,11 +1,18 @@ 1 -In th is release,ournewlog alertingwill be available!Please findoutmoreaboutit**LINK**.Furthermore, wehaveimplementedimprovements for SMBand didsomeperformance improvements. Lastly,fromnowon wenolonger supportour legacyMendixconnector(< version 4.x).1 +In the last sprint cycle, we focused on the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 35-LastLog||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.204 - Found It.WebHome||target="blank"]]. 4 4 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"]]. 5 +=====Minor changes===== 9 9 7 +* Deploy - Containers: Removed generation of unnecessary properties from the 3rd generation event streaming containers. 8 + 10 10 ====Bug fixes==== 11 -* Deploy - Architecture: The failover container will now be shown correctly. 10 + 11 +* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970) 12 +* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture. 13 +* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release. 14 +* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture. 15 + 16 +=====Infra and image changes===== 17 + 18 +* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.