Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55

From version 112.1
edited by Carlijn Kokkeler
on 2023/10/11 12:53
Change comment: There is no comment for this version
To version 174.1
edited by Carlijn Kokkeler
on 2023/12/21 16:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +211 - Log Luminary
Content
... ... @@ -1,26 +1,31 @@
1 -In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
4 4  
5 5  =====New features=====
6 6  
7 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
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.
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.
8 8  
10 +
11 +
12 +
13 +
9 9  =====Minor changes=====
10 10  
11 -* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
12 -* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
13 -* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052)
16 +* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
17 +* 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'.
18 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
14 14  
15 15  
21 +
22 +
23 +
16 16  ====Bug fixes====
17 17  
18 -* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
19 -* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
20 -* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
21 -* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
26 +* 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.
27 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container.
22 22  
23 23  
24 -=====Infra and image changes=====
25 25  
26 -* No infra and/or image changes is this release.
31 +