Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+226 - Alerting Alchemy

Author

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

Content

...	...	@@ -1,88 +1,70 @@
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!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
	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	6
7		-== **3rd generation runtime bolstering** ==
	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	8
9		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
	19	+[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
10	10
11		-//__Migration of JMS backup configuration improved__//
12		-With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
13	13
14		-//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15		-As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
	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}}
16	16
17		-//__Autogenerated exits can be deployed at once__//
18		-This release has fixed a bug that prevented you from deploying an exit flow correctly.
	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.
19	19
20		-//__Code mapping functionality available on 3rd generation runtime__//
21		-As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
	26	+{{warning}}Please note that the new queue alerting will not yet be available for models with message redelivery. {{/warning}}
22	22
23		-//__Improved the performance when activating a release__//
24		-With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
	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.
25	25
26		-//__Failing runtimes won't be restarted indefinitely anymore__//
27		-We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
	31	+//__Tenant transfer__//
	32	+A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
28	28
29		-== **Exportable Release Audit** ~* ==
	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.
30	30
31		-On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
	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.
32	32
33		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
	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'.
34	34
35		-{{warning}}Note that the following restrictions apply when exporting an audit document:
36		- * Works **only** for releases that are promoted and made active on Production
37		- * You will **only** see changes made during the **current** calendar year
38		- * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
39		- * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
40		-
41		-== **Feedback items ** ==
42		-
43		-We have also solved other feedback items besides the flow designer's critical updates.
44		-
45		-//__Improved naming convention on Store related pages__//
46		-We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
47		-
48		-//__Press "Enter" to search on multiple pages__//
49		-In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
50		-
51		-* Deploy → Deployment Plan
52		-* Deploy → Properties → History
53		-* Deploy → User Management → Roles
54		-* Manage → Error Messages → Error Messages
55		-* Manage → Error Messages → Flows with Error Messages
56		-* Manage → Error Messages → Exceptions of Error Messages
57		-* Manage → Log Entries
58		-* Manage → Alerts
59		-* Manage → Triggers
60		-* Manage → Tags – Cant find (only Gen2)
61		-* Manage → Notifications
62		-* Manage → Notification Settings
63		-* Manage → Data Usage → History
64		-* Manage → Code mappings → All tabs
65		-
66	66	== **Fancy Forum Answers** ==
67	67
68	68	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:
69	69
70		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
71		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
72		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
	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"]]
73	73
74		-== **Key takeaways** ==
	57	+== **Key Takeaways** ==
75	75
76		-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:
	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:
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.
	63	+* 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		-* Check out the release notes [here]
	65	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
83	83	* Start thinking about how the license tracker can aid your development
84	84	* Start thinking about major, minor, and patch
85		-* Upgrade to the latest build number
86	86	* Keep making great integrations
87	87
88	88	Let's stay in touch and till next time!
...	...	@@ -90,6 +90,11 @@
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 GEN3-only feature.
94		-{{/info}})))((({{toc/}}))){{/container}}
	75	+{{/info}}
	76	+)))
	77	+
	78	+(((
	79	+{{toc/}}
	80	+)))
95	95	{{/container}}
	82	+{{/container}}