Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 433.1
edited by CarlijnKokkeler
on 2024/03/27 09:30
Change comment: There is no comment for this version
To version 628.1
edited by CarlijnKokkeler
on 2024/07/29 12:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -217 - Template Tango
1 +226 - Alerting Alchemy
Content
... ... @@ -3,59 +3,41 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, new cloud templates for docker single and docker double lane are introduced. These templates enable the ability to clean H2 databases from the portal. Next to this, it is now possible to edit the trigger "More than 100 messages on queue over 10 minutes". Moroever, several copy to clipboard buttons have been added. Lastly, the runtime overview has been improved with respect to checks on the runtime version.
6 +**Hi there, eMagiz developers!** In this release,
7 7  
8 -{{info}}Reminder! As announced in our previous [[release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]], with the release of the 11th of April:
9 -
10 -* TLSv1.0 and TLSv1.1 will be deprecated.
11 -* A major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture will be released.
12 -
13 -For more information, please check out our [[release blog>>Main.Release Information.Release Blogs.216 - Hack Heaven||target="blank"]] from the previous release.{{/info}}
14 -
15 -== **Cloud Template R12 Docker - Single Lane** ==
16 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R12 Docker - Single Lane.WebHome||target="blank"]].
17 -
18 -== **Cloud Template R14 Docker - Double Lane** ==
19 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R14 Docker - Double Lane.WebHome||target="blank"]].
20 -
21 21  == **Feedback Items** ==
22 -//__Dynamic trigger__//
23 -The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
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 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.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
21 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
26 26  
27 -//__Copy to clipboard buttons__//
28 -Copy to clipboard buttons have been added to various pages:
23 +//__Tenant technical name__//
24 + The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
29 29  
30 - * Deploy agent pop-up
31 - * Create - Flow designer: Properties
32 - * Deploy - Property releases: Property details
26 +//__Tenant transfer__//
27 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
33 33  
34 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
29 +//__Property placeholder__//
30 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
35 35  
36 -//__Reset H2 database__//
37 -For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines.
38 -
39 -{{info}}Please note the following:
40 -
41 -* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
42 -* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
43 -* For on-premise runtimes, only a reset of the runtime is needed.
44 -
45 -For more information please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]]{{/info}}
46 -
47 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
48 -
49 49  == **Bug Fixes** ==
50 -//__Runtime overview improvements__//
51 -The runtime overview has been improved regarding checks on the runtime version.
52 52  
53 53  == **Fancy Forum Answers** ==
54 54  
55 55  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:
56 56  
57 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
58 -* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
38 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
39 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
40 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
59 59  
60 60  == **Key Takeaways** ==
61 61  
... ... @@ -65,7 +65,7 @@
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 66  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 -* Check out the release notes [here]
50 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
69 69  * Start thinking about how the license tracker can aid your development
70 70  * Start thinking about major, minor, and patch
71 71  * Keep making great integrations