Skip to Content

Changes for page 211 - Log Luminary

Last modified by Carlijn Kokkeler on 2024/05/22 13:36
From version 178.1
edited by Carlijn Kokkeler
on 2023/12/22 12:26
Change comment: There is no comment for this version
To version 184.1
edited by Carlijn Kokkeler
on 2024/05/22 13:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,17 +2,17 @@
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 -* 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 in an overview.
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: 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 -* Manage - Alerting: You can now add external recipients to your environment directly, like internal users.
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 +* 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.
18 18  
... ... @@ -19,9 +19,9 @@
19 19  ====Bug fixes====
20 20  
21 21  * Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
22 -* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
22 +* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
23 23  * Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container.
25 -* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal.
24 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
25 +* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
26 26  
27 27