Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 52.1
edited by Erik Bakker
on 2022/11/21 13:48
Change comment: There is no comment for this version
To version 625.1
edited by CarlijnKokkeler
on 2024/07/29 12:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -188 - Close Encounters
1 +226 - Alerting Alchemy
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,87 +1,49 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
6 +**Hi there, eMagiz developers!** In this release,
6 6  
7 -== **3rd generation runtime bolstering** ==
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 +
19 +If you 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.
8 8  
9 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
21 +//__Tenant technical name__//
22 +
23 +//__Tenant transfer__//
24 +//__Property placeholder__//
10 10  
11 -//__Migration of JMS backup configuration improved__//
12 -With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
26 +== **Bug Fixes** ==
13 13  
14 -//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15 -As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
16 -
17 -//__Autogenerated exits can be deployed at once__//
18 -This release has fixed a bug that prevented you from deploying an exit flow correctly.
19 -
20 -//__Code mapping functionality available on 3rd generation runtime__//
21 -As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
22 -
23 -//__Improved the performance when activating a release__//
24 -With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
25 -
26 -//__Failing runtimes won't be restarted indefinitely anymore__//
27 -We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
28 -
29 -== **Exportable Release Audit** ~* ==
30 -
31 -On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
32 -
33 -[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
34 -
35 -{{warning}}Note that the following restrictions apply when exporting an audit document:
36 - * Works **only** for releases that are promoted and made active on **Production**
37 - * You will **only** see changes made during the **current** calendar year
38 - * On the first of April all objects of the **last** calendar year will be **removed**{{/warning}}
39 -
40 -== **Feedback items ** ==
41 -
42 -We have also solved other feedback items besides the flow designer's critical updates.
43 -
44 -//__Improved naming convention on Store related pages__//
45 -We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
46 -
47 -//__Press "Enter" to search on multiple pages__//
48 -In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
49 -
50 -* Deploy → Deployment Plan
51 -* Deploy → Properties → History
52 -* Deploy → User Management → Roles
53 -* Manage → Error Messages → Error Messages
54 -* Manage → Error Messages → Flows with Error Messages
55 -* Manage → Error Messages → Exceptions of Error Messages
56 -* Manage → Log Entries
57 -* Manage → Alerts
58 -* Manage → Triggers
59 -* Manage → Tags – Cant find (only Gen2)
60 -* Manage → Notifications
61 -* Manage → Notification Settings
62 -* Manage → Data Usage → History
63 -* Manage → Code mappings → All tabs
64 -
65 65  == **Fancy Forum Answers** ==
66 66  
67 67  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:
68 68  
69 -* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
70 -* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
71 -* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
32 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
33 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
34 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
72 72  
73 -== **Key takeaways** ==
36 +== **Key Takeaways** ==
74 74  
75 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
38 +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:
76 76  
77 77  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  * If you have feedback or ideas for us, talk to the Platypus
79 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
42 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 80  * Clear your browser cache (Ctrl + Shift + Del)
81 -* Check out the release notes [here]
44 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
82 82  * Start thinking about how the license tracker can aid your development
83 83  * Start thinking about major, minor, and patch
84 -* Upgrade to the latest build number
85 85  * Keep making great integrations
86 86  
87 87  Let's stay in touch and till next time!
... ... @@ -89,6 +89,11 @@
89 89  {{info}}
90 90  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91 91  
92 -~*~* Indicates a GEN3-only feature.
93 -{{/info}})))((({{toc/}}))){{/container}}
54 +{{/info}}
55 +)))
56 +
57 +(((
58 +{{toc/}}
59 +)))
94 94  {{/container}}
61 +{{/container}}