Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 501.1
edited by CarlijnKokkeler
on 2024/05/06 13:12
Change comment: There is no comment for this version
To version 629.1
edited by CarlijnKokkeler
on 2024/07/29 12:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -220 - Patch Parade
1 +226 - Alerting Alchemy
Content
... ... @@ -3,60 +3,42 @@
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 +//__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 +
9 9  
10 -//__Integration pattern information__//
11 -Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
20 +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.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
22 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
14 14  
15 -//__Message queue history__//
16 -All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
24 +//__Tenant technical name__//
25 + The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
17 17  
18 -[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
27 +//__Tenant transfer__//
28 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
19 19  
20 -//__Search boxes__//
21 -Search boxes in the properties overview are now shown by default.
30 +//__Property placeholder__//
31 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
24 -
25 -//__Set as mapped__//
26 -It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
27 -
28 -[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
29 -
30 -//__SSL settings__//
31 -Changes can now be deployed on SSL level without creating a new version of a flow in Create.
32 -
33 33  == **Bug Fixes** ==
34 -//__Annotation styling__//
35 -It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
36 36  
37 -[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
38 -
39 -//__Filter rejection warnings__//
40 -A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
41 -
42 -[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
43 -
44 -//__Manage Explore__//
45 -An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
46 -
47 -//__Page refreshing__//
48 -Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
49 -
50 -//__Message redelivery__//
51 -An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page.
52 -
53 53  == **Fancy Forum Answers** ==
54 54  
55 55  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:
56 56  
57 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
58 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
59 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
39 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
40 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
41 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
60 60  
61 61  == **Key Takeaways** ==
62 62  
... ... @@ -66,7 +66,7 @@
66 66  * If you have feedback or ideas for us, talk to the Platypus
67 67  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
68 68  * Clear your browser cache (Ctrl + Shift + Del)
69 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
51 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
70 70  * Start thinking about how the license tracker can aid your development
71 71  * Start thinking about major, minor, and patch
72 72  * Keep making great integrations