Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 171.1
edited by Carlijn Kokkeler
on 2023/12/21 16:02
Change comment: There is no comment for this version
To version 152.1
edited by Carlijn Kokkeler
on 2023/10/26 12:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +207 - Aligned State
Content
... ... @@ -1,24 +1,37 @@
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 the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components and we did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
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.207 - Aligned State .WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +=====Runtime release notes=====
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.
7 +There is a new eMagiz Mendix connector available because a memory leak was found, only affecting Mendix connectors that have been migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture.
8 8  
9 9  =====Minor changes=====
10 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.
11 +* Design - Message Mapping: The button 'Import from Store' will directly open the store.
12 +* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
13 +* Create - Flow Designer: When importing items from the store, flow fragments that are hidden in Design will be listed under the versions in Create. (#1044)
14 +* Create - Flow Designer: Resources without names won't trigger error messages when users select components. (#950)
15 +* Create - Flow Designer: A migration step has been added, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
16 +* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read-only mode.
17 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
18 +* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
19 +* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
20 +* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
21 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
22 +* Manage - Data Sink: The data sink page has been moved to the “Explore” tab. (#946)
23 +* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of the configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
24 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
25 +* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
13 13  
14 14  ====Bug fixes====
15 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.
29 +* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
30 +* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
31 +* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
32 +* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
23 23  
24 24  
35 +=====Infra and image changes=====
36 +
37 +* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.