Changes for page 237 - Fabulous Flow

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-198 - Great Migration
	1	+212 - Failover Fiesta

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,24 +1,27 @@
1		-Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
	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.198 - Great Migration.WebHome||target= "blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover 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		-* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
8		-* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
9		-* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
10		-* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
11		-* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
12		-* Deploy - Architecture: You can apply your changes to environment without having an active release.
13		-* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14		-(control tower, so Gen3 only)
15		-* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
	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.
16	16
17	17	====Bug fixes====
18	18
19		-* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
20		-* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
	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)
21	21
22		-====Remarks====
23	23
24		-* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.