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,54 +3,57 @@ 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!** 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, serveral copy to clipboard buttons have been added. Lastly, the runtime overview has been improved with respect to checks on the runtime version. 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 + 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"]] 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. 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. 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 queuealertsthat you havecurrently configured tothe closestmatch in thenew alerting stack. Modelsthat areintheprocess ofmigrating to the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture duringthe timeof the release of this feature will be able to pre-configure their new queue alert triggers, butwill not be able tomake active use of them until theruntime migration has finished.25 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]] 20 20 21 -{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}} 27 +//__Copy to clipboard buttons__// 28 +Copy to clipboard buttons have been added to various pages: 22 22 23 -[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]] 30 + * Deploy agent pop-up 31 + * Create - Flow designer: Properties 32 + * Deploy - Property releases: Property details 24 24 25 -//__Tenant technical name__// 26 - The technical name of a tenant cannot be changed once the tenant has been transferred to Create. 34 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]] 27 27 28 -//__ Tenant transfer__//29 - Atenant cannot be untransferred from CreateiftheconnectorcontainerofthattenantisstillactiveinDeploy.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. 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. 39 +{{info}}Please note the following: 33 33 34 -//__Machine pop-up__// 35 -* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. 36 -* The machine health indicator has been improved visually. 37 -* Several progress bars have been improved visually. 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.{{/info}} 38 38 39 -[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]] 40 - 41 -//__Infinispan Cache Manager__// 42 -The Infinispan Cache Manager has been updated to: 43 -* Provide an additional 'transport type' to offer more means for creating a clustered setup; 44 -* Provide clearer helptexts explaining which of the options is needed and what its effect is; 45 -* Include validation on fields depending on the selected 'transport type'. 45 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]] 46 46 47 +== **Bug Fixes** == 48 +//__Runtime overview improvements__// 49 +The runtime overview has been improved regarding checks on the runtime version. 50 + 47 47 == **Fancy Forum Answers** == 48 48 49 49 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: 50 50 51 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 52 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 53 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 55 +* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]] 56 +* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]] 54 54 55 55 == **Key Takeaways** == 56 56 ... ... @@ -60,7 +60,7 @@ 60 60 * If you have feedback or ideas for us, talk to the Platypus 61 61 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 62 62 * Clear your browser cache (Ctrl + Shift + Del) 63 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]66 +* Check out the release notes [here] 64 64 * Start thinking about how the license tracker can aid your development 65 65 * Start thinking about major, minor, and patch 66 66 * Keep making great integrations