Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 85.1
edited by Erik Bakker
on 2023/06/05 16:03
on 2023/06/05 16:03
Change comment:
There is no comment for this version
To version 184.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
on 2024/01/15 14:46
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 99-HomeImprovements1 +212 - Failover Fiesta - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,20 +1,27 @@ 1 -In the last sprint cycle we havefocused onimproving various aspects of the portal functionality.Among others we focused on the next-generation architecture, the store, security and certificate management.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.1 99-HomeImprovements.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Feedback Fiesta||target="blank"]]. 4 4 5 +=====New features===== 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. 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 + 5 5 =====Minor changes===== 6 6 7 -* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately 3 months before the expiration dates of event streaming users' access certificates. 8 -* Deploy - Release: After successful machine deployments, unused runtime images will be automatically removed. This can be disabled by changing the machine step in your deployment plan. 9 -* Manage - Monitoring: HTTP statistics page now displays all of the resources. 10 -* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it. 11 -* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower. 12 +* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 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: 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 +* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards. 17 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. 12 12 13 13 ====Bug fixes==== 14 14 15 -* Create - Store: Spring Reserved words that contain * are not incorrectly replaced with the prefix of the flow. 16 -* Manage - Monitoring: When an application failed to start, not all log messages were visible in the manage phase. 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 incorrectly due to failed runtime checks. 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 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) 17 17 18 -====Remarks==== 19 19 20 -* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.