Changes for page 204 - Found It

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+204 - Found It

Author

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

Content

...	...	@@ -1,26 +1,21 @@
1		-Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments.
	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.197 - Pay Attention.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		-=====New features=====
6		-* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7		-* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
8		-
9	9	=====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.
10	10
11		-* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
12		-* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute."
13		-* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.
14		-
15	15	====Bug fixes====
16	16
17		-* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item.
18		-* Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952)
19		-* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947)
20		-* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
21		-* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments.
22		-* Design - Message Definitions: "Message format" button is also available in view mode. (#919)
	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.
23	23
24		-====Remarks====
	19	+=====Infra and image changes=====
25	25
26		-* Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture. Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off.
	21	+* Image: A fix is released with this new image to ensure that specific error messages (see above) will also be displayed in Manage.