Changes for page 211 - Log Luminary
Last modified by Carlijn Kokkeler on 2024/05/22 13:36
From version 184.1
edited by Carlijn Kokkeler
on 2024/05/22 13:36
on 2024/05/22 13:36
Change comment:
There is no comment for this version
To version 182.1
edited by Carlijn Kokkeler
on 2024/01/02 15:59
on 2024/01/02 15:59
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,16 +2,16 @@ 2 2 3 3 Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]]. 4 4 5 -====New features==== 5 +=====New features===== 6 6 7 7 * Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. 8 8 * Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 9 9 10 -====Minor changes==== 10 +=====Minor changes===== 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: Therisk 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.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'. 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.