Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 632.1
edited by CarlijnKokkeler
on 2024/07/29 12:56
Change comment: There is no comment for this version
To version 341.1
edited by CarlijnKokkeler
on 2024/01/15 14:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -226 - Alerting Alchemy
1 +212 - Failover Fiesta
Content
... ... @@ -3,45 +3,39 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release,
6 +**Hi there, eMagiz developers!** This release...
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.
8 +== **Cloud Template R20 - Double Lane** ==
18 18  
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.
10 +This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R20 - Double lane.WebHome||target="blank"]].
20 20  
21 -{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
12 +== **Cloud Template R27 - Single Lane** ==
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
14 +This release introduces a new non-service affecting cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R27 - Single lane.WebHome||target="blank"]].
24 24  
25 -//__Tenant technical name__//
26 - The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
16 +== **Feedback Items** ==
27 27  
28 -//__Tenant transfer__//
29 -A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
18 +//__Failover setup__//
19 +New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
30 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 33  
34 34  == **Bug Fixes** ==
35 35  
24 +//__Message merging tool__//
25 +The message merging tool has been fixed to allow merging a store item message model into your own message models. In some rare cases your CDM message may be broken due to incorrect data. In those cases, the message mapping and message merge functionalities will be broken as well. If this broken data is detected when navigating to CDM-message-related pages, you will be able to clean your CDM message.
26 +
27 +//__Catalog topic definitions__//
28 +It is now possible to generate a JSON Example of a topic whose schema has nested elements. Before, an error would occur when trying to generate a JSON example in this case.
29 +
36 36  == **Fancy Forum Answers** ==
37 37  
38 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:
39 39  
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"]]
34 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
35 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
36 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
43 43  
44 -== **Key Takeaways** ==
38 +== **Key takeaways** ==
45 45  
46 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:
47 47  
... ... @@ -49,7 +49,7 @@
49 49  * If you have feedback or ideas for us, talk to the Platypus
50 50  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
51 51  * Clear your browser cache (Ctrl + Shift + Del)
52 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
46 +* Check out the release notes [here]
53 53  * Start thinking about how the license tracker can aid your development
54 54  * Start thinking about major, minor, and patch
55 55  * Keep making great integrations