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 1-SwiftShift1 +226 - Alerting Alchemy - Content
-
... ... @@ -3,53 +3,28 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** This release, we have done several improvements for failover and grouping, as well as for the placement of attributes in datamodels. Next to this, we have improved the Event Catalog overview for Catalog users.It isnowalso possibleto use the back button on the eMagiz Q&A without yoursearchbeingremoved. Regarding bug fixes, the delete behaviour for containershas been improved,and scope properties will now be generated correctly. Lastly, the warning message that is given when importing an xsd has now been removed when the request or response message is empty.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. 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. 14 - 15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]] 16 - 17 -//__Attribute placements__// 18 -Some improvements regarding the placement of attributes have been done: 19 -* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add a new attribute. 20 -* Moving an attribute in the datamodel is now directly shown in the tree structure as well. 21 -* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype. 22 - 23 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.png]] 24 - 25 -//__Failover & grouping__// 26 -Some improvements regarding the widgets for failover and grouping have been done: 27 -* When executing a start/stop action on a group, the description of the step now contains the name of the group. 28 -* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group". 29 - 30 -[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]] 31 - 32 -[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]] 33 - 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 + 34 34 == **Bug Fixes** == 35 -//__XSD import__// 36 -When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion. 37 37 38 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.png]] 39 - 40 -//__Container deletion__// 41 -The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows. 42 - 43 -//__Scope properties__// 44 -We fixed an issue where the generation of scope properties was incorrect for legacy API gateway runtimes using OAuth 2.0 security scheme. 45 - 46 46 == **Fancy Forum Answers** == 47 47 48 48 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: 49 49 50 -* [[ OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]51 -* [[H TTPrequest withoutreply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]52 -* [[ All-entryAPIgatewayisnotstarting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]25 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 26 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 27 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 53 53 54 54 == **Key Takeaways** == 55 55 ... ... @@ -59,7 +59,7 @@ 59 59 * If you have feedback or ideas for us, talk to the Platypus 60 60 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 61 61 * Clear your browser cache (Ctrl + Shift + Del) 62 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.22 1-SwiftShift.WebHome||target="blank"]]37 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]] 63 63 * Start thinking about how the license tracker can aid your development 64 64 * Start thinking about major, minor, and patch 65 65 * Keep making great integrations