Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-199 - Home Improvements
	1	+210 - Deployment Delights

Author

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

Content

...	...	@@ -1,57 +1,66 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
	6	+**Hi there, eMagiz developers!** We have...
6	6
7		-== **Next generation improvements and bug fixes** ==
	8	+== **Alerts** ==
8	8
9		-//__Enhanced overview of the HTTP Statistics__//
10		-As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
	10	+//__Topic approaching max size alert__//
	11	+The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
11	11
12		-//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13		-In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
	13	+//__Missing metrics alert__//
	14	+We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
14	14
15		-{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	16	+== **Feedback Items** ==
16	16
17		-//__Forced congestion control__//
18		-To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
	18	+//__Container version overview__//
	19	+In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
19	19
20		-//__Unused images are cleaned up__//
21		-This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan.
	21	+[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
22	22
23		-//__Improved rollup and storage of metrics when running an event streaming solution__//
24		-To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
	23	+//__Unchanged containers__//
	24	+When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
25	25
26		-{{warning}} 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 July. From then on, all data before the 9th of June will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
	26	+//__Rebuilding of images__//
	27	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
27	27
28		-== **Store Improvements** ==
29	29
30		-//__Improved importing behavior for specific use cases__//
31		-Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
	30	+== **Bug Fixes** ==
32	32
33		-//__Fixed bug in creating a message mapping on top of an imported system message__//
34		-It is now possbile to create a message mapping to an imported system message from the store.
	32	+//__Runtime metrics processing__//
	33	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
35	35
36		-== **Event Streaming - Certificate Management** ==
	35	+//__Deployment plan__//
	36	+We solved a bug where a deployment step in the deployment plan could randomly get stuck.
37	37
38		-//__Expired certification notification__//
39		-As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	38	+//__Store message merging__//
	39	+The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
40	40
	41	+//__View all store items__//
	42	+An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
	43	+
	44	+//__Out of memory behavior__//
	45	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
	46	+
	47	+//__Max fetch size__//
	48	+We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
	49	+
	50	+
41	41	== **Fancy Forum Answers** ==
42	42
43	43	As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
44	44
45		-* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
46		-* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
	55	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
47	47
48	48	== **Key takeaways** ==
49	49
50		-Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	59	+Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
51	51
52	52	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53	53	* If you have feedback or ideas for us, talk to the Platypus
54		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	63	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
55	55	* Clear your browser cache (Ctrl + Shift + Del)
56	56	* Check out the release notes [here]
57	57	* Start thinking about how the license tracker can aid your development
...	...	@@ -64,6 +64,12 @@
64	64	{{info}}
65	65	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66	66
67		-~*~* Indicates a GEN3-only feature.
68		-{{/info}})))((({{toc/}}))){{/container}}
	76	+~*~* Indicates a next-generation-architecture only feature.
	77	+{{/info}}
	78	+)))
	79	+
	80	+(((
	81	+{{toc/}}
	82	+)))
69	69	{{/container}}
	84	+{{/container}}