Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 17.1
edited by eMagiz
on 2022/10/13 09:28
Change comment: There is no comment for this version
To version 631.1
edited by CarlijnKokkeler
on 2024/07/29 12:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - Get ready
1 +226 - Alerting Alchemy
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,64 +1,69 @@
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!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
6 +**Hi there, eMagiz developers!** In this release,
6 6  
7 -==**Audit trail User Management**==
8 -Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
9 -
10 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
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.
11 11  
12 -==**Next Generation Monitoring & Alerting engine**==
13 -In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
14 -
15 -* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
16 -* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
17 -* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
18 -* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
19 -* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
20 -
21 -
22 -=== **Improvements** ===
23 -
24 -* Performance Deployment plan
25 -When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
26 -
27 -* Flow Designer updates
28 -We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
29 -
30 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
31 -
32 -* Store
33 -We have fixed several smaller Store import issues to improve the user experience.
34 -
19 +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.
20 +
21 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
22 +
23 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
24 +
25 +//__Tenant technical name__//
26 + The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
27 +
28 +//__Tenant transfer__//
29 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
30 +
31 +//__Property placeholder__//
32 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
33 +
34 +== **Bug Fixes** ==
35 +
35 35  == **Fancy Forum Answers** ==
36 36  
37 -As always, a gentle reminder to all 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:
38 +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:
38 38  
39 -* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
40 -* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
40 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
41 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
42 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
41 41  
42 -== **Key takeaways** ==
44 +== **Key Takeaways** ==
43 43  
44 -Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
46 +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:
45 45  
46 46  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
47 47  * If you have feedback or ideas for us, talk to the Platypus
48 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
50 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49 49  * Clear your browser cache (Ctrl + Shift + Del)
50 -* Check out the release notes [here]
52 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
51 51  * Start thinking about how the license tracker can aid your development
52 52  * Start thinking about major, minor, and patch
53 -* Upgrade to the latest build number
54 54  * Keep making great integrations
55 -* Check out the new documentation portal.
56 56  
57 57  Let's stay in touch and till next time!
58 58  
59 59  {{info}}
60 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
60 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  
62 -~*~* Indicates a GEN3-only feature.
63 -{{/info}})))((({{toc/}}))){{/container}}
62 +{{/info}}
63 +)))
64 +
65 +(((
66 +{{toc/}}
67 +)))
64 64  {{/container}}
69 +{{/container}}