Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 09:59
From version 182.1
edited by Carlijn Kokkeler
on 2024/01/02 15:59
Change comment: There is no comment for this version
To version 184.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +212 - Failover Fiesta
Content
... ... @@ -1,6 +1,6 @@
1 -In the last sprint cycle, we focused on improving several aspects related to 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 ....
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.212 - Feedback Fiesta||target="blank"]].
4 4  
5 5  =====New features=====
6 6  
... ... @@ -11,7 +11,7 @@
11 11  
12 12  * Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13 13  * Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
14 -* Deploy - Architecture: Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
14 +* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
15 15  * Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
16 16  * Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17 17  * Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.