Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 518.1
edited by CarlijnKokkeler
on 2024/05/08 08:55
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 -220 - Patch Parade
1 +226 - Alerting Alchemy
Content
... ... @@ -3,82 +3,30 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In the last few weeks, we worked hard on solving several feedback items and bug fixes. On top of that, we have released a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] that ensures that Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. Without further ado, let us look at our improvements and bug fixes below.
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"]] 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.
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.
12 -
13 -[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
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.
17 -
18 -[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
19 -
20 -//__Search boxes__//
21 -Search boxes in the properties overview are now shown by default.
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 -//__Machine deletion__//
34 -When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted.
35 -
36 -[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
37 -
38 38  == **Bug Fixes** ==
39 -//__Annotation styling__//
40 -It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
41 41  
42 -[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
43 -
44 -//__Filter rejection warnings__//
45 -A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
46 -
47 -[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
48 -
49 -//__Manage Explore__//
50 -An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
51 -
52 -//__Page refreshing__//
53 -Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
54 -
55 -//__JMS header handling__//
56 -Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released.
57 -
58 -//__Message redelivery__//
59 -An issue has been fixed where large messages would be shown at the bottom of the Redelivery page instead of the right side of the page.
60 -
61 -//__Deployment plan__//
62 -We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps.
63 -
64 -//__Overview pages__//
65 -We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase.
66 -
67 -//__Memory check__//
68 -Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines.
69 -
70 -//__Copy password__//
71 -The copy to clipboard button now copies the actual value of passwords instead of the masked value of them.
72 -
73 -//__Gateway infra flows__//
74 -We fixed the incorrect generation of gateway infra flows for models using the OAuth 2.0 security scheme in Spring 6.
75 -
76 76  == **Fancy Forum Answers** ==
77 77  
78 78  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:
79 79  
80 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
81 -* [[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"]]
82 82  
83 83  == **Key Takeaways** ==
84 84  
... ... @@ -88,7 +88,7 @@
88 88  * If you have feedback or ideas for us, talk to the Platypus
89 89  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
90 90  * Clear your browser cache (Ctrl + Shift + Del)
91 -* 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"]]
92 92  * Start thinking about how the license tracker can aid your development
93 93  * Start thinking about major, minor, and patch
94 94  * Keep making great integrations