Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-194 - Big Leap
	1	+212 - Failover Fiesta

Author

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

Content

...	...	@@ -1,79 +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 couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
	6	+**Hi there, eMagiz developers!** This release...
6	6
7		-== **3rd generation improvements** ==
	8	+== **Feedback Items** ==
8	8
9		-//__Better feedback in error log when a corrupt stylesheet is encountered__//
10		-We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
	10	+//__Failover setup__//
	11	+New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]
11	11
12		-//__Better internal error handling to avoid unnecessary alerting and notifications__//
13		-We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
14	14
15		-//__Improved Manage Dashboard__//
16		-This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
	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.
17	17
18		-//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19		-When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
	18	+//__Broker queue metrics dashboards__//
	19	+It is now possible to select the MQTT broker in the queue metrics dashboards.
20	20
21		-//__Improved process of deploy preparation__//
22		-With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
	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.
23	23
24		-//__Improved migration of Streaming container__//
25		-When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
26	26
27		-//__Add History to Notifications in Manage__//
28		-To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
	25	+== **Bug Fixes** ==
29	29
30		-//__Improved Manage phase for Event Streaming__//
31		-Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
	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.
32	32
33		-//__Improved help text for network volumes__//
34		-With this release we have improved the help text that explains network volumes and how to use them within our solution.
	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.
35	35
36		-{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
	33	+//__Next generation block__//
	34	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
37	37
38		-== **Feedback items ** ==
39		-
40		-//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41		-With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
42		-
43		-//__User Roles are sorted alphabetically__//
44		-All user roles under User Management are now also sorted alphabetically.
45		-
46		-//__Name of keystore for user management now includes the environment__//
47		-To improve the naming of downloaded keystore that need to be distributed to external parties we have added the name of the environment to the filename. This way you can make a distinction between the various environments by looking at the filename.
48		-
49		-== **Bug fixes ** ==
50		-
51		-//__Consolidated upgrade process cloud template__//
52		-With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was actually happening in the cloud.
53		-
54		-//__Ensure users can deploy release on environments they have edit rights on__//
55		-As of now users with only limited rights in Deploy, for example, only edit rights in Test can now activate and deploy releases that are ready for other environments but need to be deployed on the environment for which they have the rights to do so.
56		-
57	57	== **Fancy Forum Answers** ==
58	58
59	59	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:
60	60
61		-* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
62		-* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
63		-* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
	40	+* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
64	64
65	65	== **Key takeaways** ==
66	66
67		-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:
68	68
69	69	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70	70	* If you have feedback or ideas for us, talk to the Platypus
71		-* 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.
72	72	* Clear your browser cache (Ctrl + Shift + Del)
73	73	* Check out the release notes [here]
74	74	* Start thinking about how the license tracker can aid your development
75	75	* Start thinking about major, minor, and patch
76		-* Upgrade to the latest build number
77	77	* Keep making great integrations
78	78
79	79	Let's stay in touch and till next time!
...	...	@@ -81,6 +81,11 @@
81	81	{{info}}
82	82	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83	83
84		-~*~* Indicates a GEN3-only feature.
85		-{{/info}})))((({{toc/}}))){{/container}}
	60	+{{/info}}
	61	+)))
	62	+
	63	+(((
	64	+{{toc/}}
	65	+)))
86	86	{{/container}}
	67	+{{/container}}