Changes for page 204 - Found It

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-198 - Great Migration
	1	+204 - Found It

Author

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

Content

...	...	@@ -1,24 +1,21 @@
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 the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact.
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.204 - Found It.WebHome||target="blank"]].
4	4
5	5	=====Minor changes=====
	6	+* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change and can be multiply selected.
	7	+* Deploy - Architecture: The container calculations are improved. For event streaming containers these show the amount of topic proccessers deployed. For gateway containers these represent the amount of operations deployed on a container. For JMS containers these represent the amount of message queues deployed. The other types of containers display the amount of intergrations deployed.
	8	+* Create - 3rd Generation runtime migration: Your containers will be validated for 3rd Generation runtimes first before you approve the migration.
	9	+* Deploy - Architecture: Users with edit rights in deploy can edit certificates.
	10	+* Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
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.
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.
	14	+* Deploy - Releases: Container images are rebuilt correctly after changing a container’s IaaS. (#970)
	15	+* Manage - Error messages: Error messages with a lengthy message history will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
	16	+* Deploy - Releases: When a user activates a release containing nested properties and the property is not created, we show it now as missing. We add the property placeholder after the user tries to activate the release.
	17	+* Manage - Error messages: Error messages with a stack trace larger than 32kb will also be displayed. This change only impacts containers that work on the 3rd generation architecture.
21	21
22		-====Remarks====
	19	+=====Infra and image changes=====
23	23
24		-* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
	21	+* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.