Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 625.1
edited by CarlijnKokkeler
on 2024/07/29 12:28
Change comment: There is no comment for this version
To version 94.1
edited by Erik Bakker
on 2023/03/17 08:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -226 - Alerting Alchemy
1 +194 - Giant Leap
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,49 +1,82 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release,
5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
7 7  
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.
7 +== **3rd generation improvements** ==
20 20  
21 -//__Tenant technical name__//
22 -
23 -//__Tenant transfer__//
24 -//__Property placeholder__//
9 +//__Better feedback in the error log when a corrupt stylesheet is encountered__//
10 +We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
25 25  
26 -== **Bug Fixes** ==
12 +//__Better internal error handling to avoid unnecessary alerting and notifications__//
13 +We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
27 27  
15 +//__Improved Manage Dashboard__//
16 +This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
17 +
18 +//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 +When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. The opposite happens when the slot wakeup is triggered. As a result, not only the cloud runtimes are started but also all on-premise runtimes.
20 +
21 +//__Improved process of deploy preparation__//
22 +With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
23 +
24 +//__Improved migration of Streaming container__//
25 +When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
26 +
27 +//__Add History to Notifications in Manage__//
28 +To improve the auditability of our platform, we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way, it is always visible when the notifications were paused and who paused or unpaused the notifications.
29 +
30 +//__Improved Manage phase for Event Streaming__//
31 +Based on the feedback on our first iteration of the Manage phase for Event Streaming, we have improved the graphs and the calculations that fill the graphs with values. On top of that, we have added help texts to clarify what each chart our table displays to you.
32 +
33 +//__Improved help text for network volumes__//
34 +With this release, we have improved the help text that explains network volumes and how to use them within our solution.
35 +
36 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
37 +
38 +== **Feedback items ** ==
39 +
40 +//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41 +With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
42 +
43 +//__User Roles are sorted alphabetically__//
44 +All user roles under User Management are now also sorted alphabetically.
45 +
46 +//__Name of keystore for user management now includes the environment__//
47 +To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
48 +
49 +//__Improved Topic calculations in Design Architecture__//
50 +Following our earlier improvements on the best practice configuration of topics we have now additionally updated the calculations on "Topic Storage" level to ensure that the configuration of a user is related to the total Assigned Size on "Topic Storage" level.
51 +
52 +== **Bug fixes ** ==
53 +
54 +//__Consolidated upgrade process cloud template__//
55 +With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
56 +
57 +//__Ensure users can deploy release on environments they have edit rights on__//
58 +Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
59 +
28 28  == **Fancy Forum Answers** ==
29 29  
30 30  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:
31 31  
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"]]
64 +* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
65 +* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
66 +* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
35 35  
36 -== **Key Takeaways** ==
68 +== **Key takeaways** ==
37 37  
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:
70 +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:
39 39  
40 40  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
41 41  * If you have feedback or ideas for us, talk to the Platypus
42 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
74 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
43 43  * Clear your browser cache (Ctrl + Shift + Del)
44 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
76 +* Check out the release notes [here]
45 45  * Start thinking about how the license tracker can aid your development
46 46  * Start thinking about major, minor, and patch
79 +* Upgrade to the latest build number
47 47  * Keep making great integrations
48 48  
49 49  Let's stay in touch and till next time!
... ... @@ -51,11 +51,6 @@
51 51  {{info}}
52 52  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53 53  
54 -{{/info}}
55 -)))
56 -
57 -(((
58 -{{toc/}}
59 -)))
87 +~*~* Indicates a GEN3-only feature.
88 +{{/info}})))((({{toc/}}))){{/container}}
60 60  {{/container}}
61 -{{/container}}