Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-199 - Home Improvements
	1	+212 - Failover Fiesta

Author

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

Content

...	...	@@ -1,62 +1,55 @@
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!** This release...
6	6
7		-== **Next generation improvements and bug fixes** ==
	8	+== **Feedback Items** ==
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	+//__Failover setup__//
	11	+New components have been created to support a failover setup. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V2.1.0||target="blank"]]
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	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
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}}
	15	+//__External recipients emailaddress__//
	16	+The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
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	+//__Broker queue metrics dashboards__//
	19	+It is now possible to select the MQTT broker in the queue metrics dashboards.
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	+//__Runtime image version__//
	22	+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.
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.
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}}
	25	+== **Bug Fixes** ==
27	27
28		-== **Store Improvements** ==
	27	+//__Message throughput__//
	28	+The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
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	+//__Cloud template upgrade incorrect rollback__//
	31	+An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
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.
	33	+//__Next generation block__//
	34	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
35	35
36		-== **Event Streaming - Certificate Management** ==
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]].
40		-
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"]]
	40	+* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||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:
	44	+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.
	48	+* 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
58	58	* Start thinking about major, minor, and patch
59		-* Upgrade to the latest build number
60	60	* Keep making great integrations
61	61
62	62	Let's stay in touch and till next time!
...	...	@@ -64,6 +64,11 @@
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}}
	60	+{{/info}}
	61	+)))
	62	+
	63	+(((
	64	+{{toc/}}
	65	+)))
69	69	{{/container}}
	67	+{{/container}}