Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 281.2
edited by CarlijnKokkeler
on 2023/12/04 15:08
Change comment: Update document after refactoring.
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 -210 - Deployment Delights
1 +226 - Alerting Alchemy
Content
... ... @@ -3,58 +3,32 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have...
6 +**Hi there, eMagiz developers!** In this release,
7 7  
8 -== **Alerts** ==
9 -
10 -//__Topic approaching max size alert__//
11 -The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
12 -
13 -//__Missing metrics alert__//
14 -We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
15 -
16 16  == **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.
17 17  
18 -//__Container version overview__//
19 -In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
20 -
21 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
22 -
23 -//__Unchanged containers__//
24 -When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
25 -
26 -//__Rebuilding of images__//
27 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
28 -
29 -
30 30  == **Bug Fixes** ==
31 31  
32 -//__Runtime metrics processing__//
33 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
34 -
35 -//__Deployment plan__//
36 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
37 -
38 -//__Store message merging__//
39 -The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
40 -
41 -//__View all store items__//
42 -An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
43 -
44 -//__Out of memory behavior__//
45 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
46 -
47 -//__Max fetch size__//
48 -We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
49 -
50 -
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||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"]]
56 56  
57 -== **Key takeaways** ==
31 +== **Key Takeaways** ==
58 58  
59 59  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
60 60  
... ... @@ -62,10 +62,9 @@
62 62  * If you have feedback or ideas for us, talk to the Platypus
63 63  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64 64  * Clear your browser cache (Ctrl + Shift + Del)
65 -* Check out the release notes [here]
39 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
66 66  * Start thinking about how the license tracker can aid your development
67 67  * Start thinking about major, minor, and patch
68 -* Upgrade to the latest build number
69 69  * Keep making great integrations
70 70  
71 71  Let's stay in touch and till next time!
... ... @@ -73,7 +73,6 @@
73 73  {{info}}
74 74  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75 75  
76 -~*~* Indicates a next-generation-architecture only feature.
77 77  {{/info}}
78 78  )))
79 79