Skip to Content

Changes for page 235 - Last Log

Last modified by CarlijnKokkeler on 2024/12/04 14:02
From version 78.1
edited by Erik Bakker
on 2023/05/12 08:02
Change comment: There is no comment for this version
To version 348.1
edited by CarlijnKokkeler
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 -197 - Pay Attention
1 +235 - Last Log
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,21 +1,11 @@
1 -Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments.
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.197 - Pay Attention.WebHome||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=====
6 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7 -* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
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"]].
8 8  
9 -=====Minor changes=====
10 -
11 -* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
12 -* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute."
13 -* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.
14 -
15 15  ====Bug fixes====
16 -
17 -* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item.
18 -* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models.
19 -* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
20 -* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again.
21 -* Design - Message Definitions: "Message format" button is also available in view mode. (#919)
11 +* Deploy - Architecture: The failover container will now be shown correctly.