Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Max Verstappen
	1	+197 - Pay Attention

Author

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

Content

...	...	@@ -1,83 +1,78 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** We have done .....
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
7	7
8		-{{warning}}
9		-Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10		-{{/warning}}
	7	+== **Event streaming alerting** ==
11	11
12		-== **Quicker Deployment Plan** ==
	9	+With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it.
13	13
14		-We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now!
	11	+The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication that messages might be deleted before consumer groups had the option to consume the messages.
15	15
16		-== **Next Generation Architecture Default** ==
	13	+The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
17	17
18		-With this release, the next generation architecture will become the default. New models will use this generation as default.
	15	+[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
19	19
20		-[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
	17	+The first new "dynamic" alert allows you to raise an alert once the total number of messages on one (or more topics) is less than a certain number per defined time unit. So for example you can configure an alert once the number of message placed on a topic called "Exception" is less than 15 messages within 5 minutes.
21	21
22		-== **Cloud Template R11 Docker - Single Lane** ==
	19	+[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
23	23
24		-This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
	21	+The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
25	25
26		-== **Cloud Template R13 Docker - Double Lane** ==
	23	+For more information on the generic way of working surrounding alerting please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
27	27
28		-This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
	25	+== **3rd generation improvements** ==
29	29
30		-== **Feedback Items** ==
	27	+//__Event Streaming statistics completion__//
	28	+In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
31	31
32		-//__Unused properties overview__//
33		-In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
	30	+//__Deployments on next generation architecture__//
	31	+This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
34	34
35		-* Not used by any runtime that is in the Create phase release.
36		-* Not required by a flow that is in the Create phase release.
37		-* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
	33	+//__Clean queues option__//
	34	+This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
38	38
39		-//__Send build requests asynchronously__//
40		-The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
	36	+== **Feedback items ** ==
41	41
42		-//__Queue explorer milliseconds__//
43		-The queue browser now displays milliseconds in the timestamps.
	38	+//__On-premise containers are started upon slot wakeup__//
	39	+With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
44	44
45		-//__Cancel and next buttons order__//
46		-The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
	41	+//__Resource path is shown to the user__//
	42	+You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
47	47
48		-//__Unused images__//
49		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
	44	+//__Flow designer improvements__//
	45	+With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
50	50
51		-//__Carwash logging__//
52		-A new logging feature enabling us to make better choices in encryption standards will be released.
	47	+//__Improved capabilities of a company contact__//
	48	+With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
53	53
54		-//__Static alerts queue consumers__//
55		-Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
	50	+== **Bug fixes ** ==
56	56
57		-== **Bug Fixes** ==
	52	+//__Optional API parameters are handled correctly__//
	53	+Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
58	58
59		-//__Flow Designer connection line__//
60		-In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
	55	+//__Without CDM rights nothing related to any data model can be edited anymore__//
	56	+With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
61	61
62		-//__Portal for migrated models__//
63		-We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
	58	+//__Improved sorting of Design and Deploy archticture__//
	59	+With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
64	64
65		-//__Error channel inbounds__//
66		-We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
67		-
68	68	== **Fancy Forum Answers** ==
69	69
70	70	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:
71	71
72		-* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	65	+* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	66	+* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
	67	+* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
73	73
74	74	== **Key takeaways** ==
75	75
76		-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:
	71	+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:
77	77
78	78	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
79	79	* If you have feedback or ideas for us, talk to the Platypus
80		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	75	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
81	81	* Clear your browser cache (Ctrl + Shift + Del)
82	82	* Check out the release notes [here]
83	83	* Start thinking about how the license tracker can aid your development
...	...	@@ -90,12 +90,6 @@
90	90	{{info}}
91	91	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
92	92
93		-~*~* Indicates a next-generation-architecture only feature.
94		-{{/info}}
95		-)))
96		-
97		-(((
98		-{{toc/}}
99		-)))
	88	+~*~* Indicates a GEN3-only feature.
	89	+{{/info}})))((({{toc/}}))){{/container}}
100	100	{{/container}}
101		-{{/container}}