Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 26-AlertingAlchemy1 +217 - Template Tango - Content
-
... ... @@ -3,30 +3,51 @@ 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!** 7 7 8 +== **Cloud Template R12 Docker - Single Lane** == 9 +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. 10 + 11 +== **Cloud Template R14 Docker - Double Lane** == 12 +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. 13 + 8 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"]] stack, 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 latest generation runtime, you will be migrated on the day of release. 15 +//__Custom trigger__// 16 +The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger. 20 20 18 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 19 + 20 +//__Copy to clipboard buttons__// 21 +Copy to clipboard buttons have been added to various pages: 22 + 23 + * Deploy agent pop-up 24 + * Create - Flow designer: Properties 25 + * Deploy - Property releases: Property details 26 + 27 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] 28 + 29 +//__Remove H2 database__// 30 +For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following: 31 + 32 +* Only H2 databases that are registered under the standard eMagiz data folder will be removed. 33 +* 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. 34 +* For on-premise runtimes, only a reset of the runtime is needed. 35 + 36 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 37 + 21 21 == **Bug Fixes** == 39 +//__Runtime overview improvements__// 40 +The runtime overview has been improved regarding checks on the runtime version. 22 22 23 23 == **Fancy Forum Answers** == 24 24 25 25 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: 26 26 27 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 28 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 29 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 46 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]] 47 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]] 48 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]] 49 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]] 50 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]] 30 30 31 31 == **Key Takeaways** == 32 32 ... ... @@ -36,7 +36,7 @@ 36 36 * If you have feedback or ideas for us, talk to the Platypus 37 37 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 38 38 * Clear your browser cache (Ctrl + Shift + Del) 39 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]60 +* Check out the release notes [here] 40 40 * Start thinking about how the license tracker can aid your development 41 41 * Start thinking about major, minor, and patch 42 42 * Keep making great integrations