Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 521.1
edited by CarlijnKokkeler
on 2024/05/21 10:56
Change comment: There is no comment for this version
To version 631.1
edited by CarlijnKokkeler
on 2024/07/29 12:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +226 - Alerting Alchemy
Content
... ... @@ -3,29 +3,43 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!** In this release,
7 7  
8 8  == **Feedback Items** ==
9 -//__Q&A search__//
10 -Search results are now persisted when pressing the back button after opening a question in the community Q & A.
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.
11 11  
12 -//__Event catalog__//
13 -For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
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.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
21 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
16 16  
17 -== **Bug Fixes** ==
18 -//__XSD import__//
19 -When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
23 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
25 +//__Tenant technical name__//
26 + The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
22 22  
28 +//__Tenant transfer__//
29 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
30 +
31 +//__Property placeholder__//
32 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
33 +
34 +== **Bug Fixes** ==
35 +
23 23  == **Fancy Forum Answers** ==
24 24  
25 25  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:
26 26  
27 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
28 -* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]]
40 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
41 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
42 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
29 29  
30 30  == **Key Takeaways** ==
31 31  
... ... @@ -35,7 +35,7 @@
35 35  * If you have feedback or ideas for us, talk to the Platypus
36 36  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
37 37  * Clear your browser cache (Ctrl + Shift + Del)
38 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
52 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
39 39  * Start thinking about how the license tracker can aid your development
40 40  * Start thinking about major, minor, and patch
41 41  * Keep making great integrations