Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
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 166.1
edited by Carlijn Kokkeler
on 2023/12/04 15:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +210 - Deployment Delights
Content
... ... @@ -1,19 +1,24 @@
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 improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
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.210 - Deployment Delights||target="blank"]].
4 4  
5 5  =====New features=====
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 in the Create phase section.
7 7  
8 -
9 9  =====Minor changes=====
10 10  
11 -* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
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.
12 12  
13 -
14 -
15 15  ====Bug fixes====
16 16  
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.
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.
17 17  
18 18  
19 -