Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -22 6-Alerting Alchemy1 +222 - Flee Frustration - Content
-
... ... @@ -3,28 +3,31 @@ 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!** 7 7 8 8 == **Feedback Items** == 9 -//__Queue alerting__// 10 -Alerting for message queues has been improved, 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 - 9 + 10 + 11 + 12 + 19 19 == **Bug Fixes** == 14 +//__Trigger activation__// 15 +Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed. 20 20 17 +//__Trigger activation__// 18 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. 19 + 20 + IMAGE 21 +[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]] 22 + 23 + 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 -* [[ Transactionfailedandhasbeenrolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]26 -* [[H owto calculateHMAC-SHA1signatureforwebhookverification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]27 -* [[ How canyouconvertan jsonarrayto xml withthenewapproach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]28 +* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]] 29 +* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]] 30 +* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]] 28 28 29 29 == **Key Takeaways** == 30 30 ... ... @@ -34,7 +34,7 @@ 34 34 * If you have feedback or ideas for us, talk to the Platypus 35 35 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 36 36 * Clear your browser cache (Ctrl + Shift + Del) 37 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.22 5-Pop-upParty.WebHome||target="blank"]]40 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]] 38 38 * Start thinking about how the license tracker can aid your development 39 39 * Start thinking about major, minor, and patch 40 40 * Keep making great integrations