Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-226 - Alerting Alchemy
	1	+209 - Max Verstappen

Content

...	...	@@ -3,57 +3,62 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** The past few weeks we have worked hard to release our new queue alerting design. Please find out all new features in our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning. Note that the new queue alerting will not yet be availalbe for queues with message redelivery. Next to alerting, we have worked on tenant items, machine pop-ups and progress bars, as well as the Infinispan Cache Manager. Find out all below!
	6	+**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
7	7
8		-== **Feedback Items** ==
9		-//__Queue alerting__//
10		-Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, which includes the following improvements:
11		-* New UI that shows all queues and the alerting that is active on them.
12		-* Every queue in the model will be automatically added to the list of queues in Manage - Alerting.
13		-* Triggers of a queue will be automatically enabled or disabled based on whether that queue is included in the release.
14		-* Added 2 new trigger types "inactivity check" and "periodic activity check" that replace the "queue throughput" alert.
15		-** These checks can now run for a (very) long time, whereas the "queue throughput" was limited by 1 hour.
16		-* The alert generation has been solidified to reduce the likelihood that your alerting is affected with false positives or false negatives during eMagiz maintenance.
17		-* When the same check of multiple queues trigger at the same time, the alerts will be aggregated into a single summarized email instead of a single email per alert.
	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}}
18	18
19		-If your model is running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, you will be migrated on the day of release. eMagiz will transfer the queue alerts that you have currently configured to the closest match in the new alerting stack. Models that are in the process of migrating to the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture during the time of the release of this feature will be able to pre-configure their new queue alert triggers, but will not be able to make active use of them until the runtime migration has finished.
	12	+== **Quicker Deployment Plan Execution** ==
20	20
21		-{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
	14	+We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. So, the deployment plan will be finished much quicker now!
22	22
23		-{{info}}Please check out our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning for an elaborate explanation of our new queue alerting design. {{/info}}
	16	+== **Next Generation Architecture Default** ==
24	24
25		-[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
	18	+With this release, the next generation architecture will become the default. From now on, new models will then use this generation as the default architecture.
26	26
27		-//__Tenant technical name__//
28		-The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
	20	+[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
29	29
30		-//__Tenant transfer__//
31		-A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
	22	+== **Cloud Template R11 Docker - Single Lane** ==
32	32
33		-//__Property placeholder__//
34		-A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
	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"]].
35	35
36		-//__Machine pop-up__//
37		-* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
38		-* The machine health indicator has been improved visually.
39		-* Several progress bars have been improved visually.
	26	+== **Cloud Template R13 Docker - Double Lane** ==
40	40
41		-[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]]
42		-
43		-//__Infinispan Cache Manager__//
44		-The Infinispan Cache Manager has been updated to:
45		-* Provide an additional 'transport type' to offer more means for creating a clustered setup;
46		-* Provide clearer helptexts explaining which of the options is needed and what its effect is;
47		-* Include validation on fields depending on the selected 'transport type'.
	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"]].
48	48
	30	+== **Feedback Items** ==
	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:
	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.
	38	+
	39	+[[image:Main.Images.Release Blog.WebHome@release-blog-209-unused-properties-overview.png]]
	40	+
	41	+//__Queue explorer milliseconds__//
	42	+The queue browser now displays milliseconds in the timestamps.
	43	+
	44	+//__Static alerts queue consumers__//
	45	+Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
	46	+
	47	+== **Bug Fixes** ==
	48	+
	49	+//__Flow Designer connection line__//
	50	+In the Flow Designer an issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
	51	+
	52	+//__Portal for migrated models__//
	53	+We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
	54	+
49	49	== **Fancy Forum Answers** ==
50	50
51	51	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:
52	52
53		-* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]
54		-* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]
	59	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
55	55
56		-== **Key Takeaways** ==
	61	+== **Key takeaways** ==
57	57
58	58	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:
59	59
...	...	@@ -61,9 +61,10 @@
61	61	* If you have feedback or ideas for us, talk to the Platypus
62	62	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
63	63	* Clear your browser cache (Ctrl + Shift + Del)
64		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
	69	+* Check out the release notes [here]
65	65	* Start thinking about how the license tracker can aid your development
66	66	* Start thinking about major, minor, and patch
	72	+* Upgrade to the latest build number
67	67	* Keep making great integrations
68	68
69	69	Let's stay in touch and till next time!
...	...	@@ -71,6 +71,7 @@
71	71	{{info}}
72	72	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73	73
	80	+~*~* Indicates a next-generation-architecture only feature.
74	74	{{/info}}
75	75	)))
76	76