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	+214 - System Symphony

Content

...	...	@@ -3,41 +3,43 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** In this release,
	6	+**Hi there, eMagiz developers!** In this release, ...
7	7
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		-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.
	10	+//__Update flows__//
	11	+Support for deploying to on premise Windows machines has been delivered.
20	20
21		-{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
	13	+//__Image versions__//
	14	+The deletion of releases with deployed container versions will not be blocked anymore. Automated release clean up behaviour will also not exclude these releases from deletion. Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases.
22	22
23		-//__Tenant technical name__//
24		- The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
	16	+//__Adding multiple attributes__//
	17	+It is now possible to add multiple existing attributes to an entity at once.
25	25
26		-//__Tenant transfer__//
27		-A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
	19	+//__Monitoring graphs__//
	20	+The monitoring graphs can now show data up to the last 30 days.
28	28
29		-//__Property placeholder__//
30		-A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
31		-
32	32	== **Bug Fixes** ==
	23	+//__Failover group helptext__//
	24	+The helptext of the Group attribute has been improved.
33	33
	26	+[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
	27	+
	28	+//__Failover group refresh__//
	29	+A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in Group tab of "Start/Stop Flows" screen.
	30	+
	31	+[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
	32	+
	33	+//__Resource paths__//
	34	+After migrating a gateway to Gen3, the path references in the event processors would be broken. This has been fixed.
	35	+
34	34	== **Fancy Forum Answers** ==
35	35
36	36	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:
37	37
38		-* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
39		-* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
40		-* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
	40	+* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
	41	+* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
	42	+* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
41	41
42	42	== **Key Takeaways** ==
43	43
...	...	@@ -47,7 +47,7 @@
47	47	* If you have feedback or ideas for us, talk to the Platypus
48	48	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49	49	* Clear your browser cache (Ctrl + Shift + Del)
50		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
	52	+* Check out the release notes [here]
51	51	* Start thinking about how the license tracker can aid your development
52	52	* Start thinking about major, minor, and patch
53	53	* Keep making great integrations