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	+210 - Deployment Delights

Content

...	...	@@ -3,59 +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!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7	7
	8	+== **Alerts** ==
	9	+
	10	+//__Topic approaching max size alert__//
	11	+The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
	12	+
	13	+//__Missing metrics alert__//
	14	+We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
	15	+
8	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.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
	18	+//__Improved release build process__//
	19	+When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
20	20
	21	+//__Container version overview__//
	22	+Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
21	21
22		-{{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}}
	24	+[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
23	23
24		-eMagiz will migrate your dynamic queue alerts on the **release day** when you are **fully** or **partially** migrated to the [[current runtime architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]. When doing so, we will configure the new queue alert in a similar fashion to best match its current behaviour. Note that the queue alerting will only function for models that are **fully** migrated to the [[current runtime architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]. Should you want to change or create new queue alerts, you can do so starting the day **after** the release to avoid conflicts with our migration.
	26	+//_Improved deployment process_//
	27	+The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
25	25
26		-{{warning}}Please note that the new queue alerting will not yet be available for models with message redelivery. {{/warning}}
	29	+//__Rebuilding of images__//
	30	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
27	27
28		-//__Tenant technical name__//
29		-For multi-tenant system integrations, the technical name of a tenant cannot be changed once the tenant has been transferred to Create.
	32	+== **Bug Fixes** ==
30	30
31		-//__Tenant transfer__//
32		-A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
	34	+//__Runtime metrics processing__//
	35	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
33	33
34		-//__Property placeholder__//
35		-A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
	37	+//__Deployment plan__//
	38	+We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
36	36
37		-//__Machine details pop-up__//
38		-* The machine details pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
39		-* The machine health indicator has been improved visually.
40		-* Several progress bars have been improved visually.
	40	+//__View all store items__//
	41	+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.
41	41
42		-[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]]
43		-
44		-//__Infinispan Cache Manager__//
45		-The Infinispan Cache Manager has been updated to:
46		-* Provide an additional 'transport type' to offer more means for creating a clustered setup;
47		-* Provide clearer helptexts explaining which of the options is needed and what its effect is;
48		-* Include validation on fields depending on the selected 'transport type'.
	43	+//__Out of memory behavior__//
	44	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
49	49
	46	+//__Max fetch size__//
	47	+In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
	48	+
50	50	== **Fancy Forum Answers** ==
51	51
52	52	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:
53	53
54		-* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]
55		-* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]
	53	+* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
	54	+* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
	55	+* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
	56	+* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
	57	+* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
56	56
57		-== **Key Takeaways** ==
58	58
	60	+== **Key takeaways** ==
	61	+
59	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:
60	60
61	61	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
...	...	@@ -62,9 +62,10 @@
62	62	* If you have feedback or ideas for us, talk to the Platypus
63	63	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64	64	* Clear your browser cache (Ctrl + Shift + Del)
65		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
	68	+* Check out the release notes [here]
66	66	* Start thinking about how the license tracker can aid your development
67	67	* Start thinking about major, minor, and patch
	71	+* Upgrade to the latest build number
68	68	* Keep making great integrations
69	69
70	70	Let's stay in touch and till next time!
...	...	@@ -72,6 +72,7 @@
72	72	{{info}}
73	73	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74	74
	79	+~*~* Indicates a next-generation-architecture only feature.
75	75	{{/info}}
76	76	)))
77	77