Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 519.1
edited by CarlijnKokkeler
on 2024/05/21 10:45
Change comment: There is no comment for this version
To version 624.1
edited by CarlijnKokkeler
on 2024/07/29 12:24
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,27 +3,30 @@
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"]] stack, 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 +
19 +If you model is running on the latest generation runtime, you will be migrated on the day of release.
11 11  
12 -//__Event catalog__//
13 -We have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
14 -
15 -
16 16  == **Bug Fixes** ==
17 -//__XSD import__//
18 -When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
19 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]]
20 20  
21 21  == **Fancy Forum Answers** ==
22 22  
23 23  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:
24 24  
25 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
26 -* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]]
27 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
28 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
29 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
27 27  
28 28  == **Key Takeaways** ==
29 29  
... ... @@ -33,7 +33,7 @@
33 33  * If you have feedback or ideas for us, talk to the Platypus
34 34  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
35 35  * Clear your browser cache (Ctrl + Shift + Del)
36 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
39 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
37 37  * Start thinking about how the license tracker can aid your development
38 38  * Start thinking about major, minor, and patch
39 39  * Keep making great integrations