Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 47.1
edited by Erik Bakker
on 2022/11/21 13:09
on 2022/11/21 13:09
Change comment:
There is no comment for this version
To version 638.1
edited by CarlijnKokkeler
on 2024/07/29 13:19
on 2024/07/29 13:19
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 188-CloseEncounters1 +226 - Alerting Alchemy - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,91 +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!** Th is releaseischaracterizedmainlybyour effortsto bolster our3rdgenerationruntimeandallits interactions.Furthermore,someminorfixes and betafeatureswill be released to thecommunity.6 +**Hi there, eMagiz developers!** The past few weeks we have worked hard to release our new queue alerting design. Please find out all new features in our [[Standard Alerting eMagiz microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]]. Note that the new queue alerting will not yet be availalbe for queues with message redelivery. Next to alerting, we have worked on tenant items, machine pop-ups and progress bars, and the Infinispan Cache Manager. Find out all below! 6 6 7 -== **3rd generation runtime bolstering** == 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 8 9 - Thisreleasewillintroducevariousimprovementsfor our 3rdgenerationruntime. Belowyou willfind themostnoteworthyenhancementswemade to the3rd generation runtime andits interactionwith theportal.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 10 11 -//__Migration of JMS backup configuration improved__// 12 -With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime. 21 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}} 13 13 14 -//__Prechecks on Upgrade option made available for 3rd generation runtime__// 15 -As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture. 23 +{{info}}Please check out our [[Standard Alerting eMagiz microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] for an elaborate explanation of our new queue alerting design. {{/info}} 16 16 17 -//__Autogenerated exits can be deployed at once__// 18 -This release has fixed a bug that prevented you from deploying an exit flow correctly. 25 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]] 19 19 20 -//__ Codemappingfunctionalityavailableon3rd generation runtime__//21 - Asofthis release,codemappingfunctionalityisalsoavailablefor the3rdgenerationruntime.This removestherestrictionon migratingtothenew 3rd generationruntimeforourclientsthat use the codemapping functionality.27 +//__Tenant technical name__// 28 + The technical name of a tenant cannot be changed once the tenant has been transferred to Create. 22 22 23 -//__ Improved the performance whenactivatingarelease__//24 - Withthis release,theperformanceofactivating arelease hasimprovedconsiderably.Thismeanslesswaitingtime whenactivatinga release.30 +//__Tenant transfer__// 31 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. 25 25 26 -//__ Failingruntimes won't berestarted indefinitely anymore__//27 - Wehaveput acaponthis behaviortopreventyour logs from explodingduetoafailingruntimebeingrestartedindefinitely.As of thisrelease,five attemptswill bemade to restartafailingruntime.Iftheruntimecannot start correctlyaftertheseattempts,theruntimewill bestopped.33 +//__Property placeholder__// 34 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal. 28 28 29 -== **Exportable Release Audit** ~* == 36 +//__Machine pop-up__// 37 +* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. 38 +* The machine health indicator has been improved visually. 39 +* Several progress bars have been improved visually. 30 30 31 -On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release. 41 +[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]] 42 + 43 +//__Infinispan Cache Manager__// 44 +The Infinispan Cache Manager has been updated to: 45 +* Provide an additional 'transport type' to offer more means for creating a clustered setup; 46 +* Provide clearer helptexts explaining which of the options is needed and what its effect is; 47 +* Include validation on fields depending on the selected 'transport type'. 32 32 33 -[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]] 34 - 35 -{{warning}}Note that the following restrictions apply when exporting an audit document: 36 - * Changes made on definition and transformation level are **not** restored 37 - * You will **not** be able to restore to any flow version that was created before October 17th, 2022 38 - * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back 39 - * Your restored flow version will **not** be automatically committed to Deploy{{/warning}} 40 - 41 -== **Feedback items ** == 42 - 43 -We have also solved other feedback items besides the flow designer's critical updates. 44 - 45 -//__Data Sink Refactor__// 46 -We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end, we will contact you separately. 47 - 48 -//__Improved naming convention on Store related pages__// 49 -We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns. 50 - 51 -//__Press "Enter" to search on multiple pages__// 52 -In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows. 53 - 54 -* Deploy → Deployment Plan 55 -* Deploy → Properties → History 56 -* Deploy → User Management → Roles 57 -* Manage → Error Messages → Error Messages 58 -* Manage → Error Messages → Flows with Error Messages 59 -* Manage → Error Messages → Exceptions of Error Messages 60 -* Manage → Log Entries 61 -* Manage → Alerts 62 -* Manage → Triggers 63 -* Manage → Tags – Cant find (only Gen2) 64 -* Manage → Notifications 65 -* Manage → Notification Settings 66 -* Manage → Data Usage → History 67 -* Manage → Code mappings → All tabs 68 - 69 69 == **Fancy Forum Answers** == 70 70 71 71 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: 72 72 73 -* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]] 74 -* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]] 75 -* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]] 53 +* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]] 54 +* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]] 76 76 77 -== **Key takeaways** ==56 +== **Key Takeaways** == 78 78 79 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:58 +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: 80 80 81 81 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 82 82 * If you have feedback or ideas for us, talk to the Platypus 83 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 62 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 84 84 * Clear your browser cache (Ctrl + Shift + Del) 85 -* Check out the release notes [here] 64 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]] 86 86 * Start thinking about how the license tracker can aid your development 87 87 * Start thinking about major, minor, and patch 88 -* Upgrade to the latest build number 89 89 * Keep making great integrations 90 90 91 91 Let's stay in touch and till next time! ... ... @@ -93,6 +93,11 @@ 93 93 {{info}} 94 94 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 95 95 96 -~*~* Indicates a GEN3-only feature. 97 -{{/info}})))((({{toc/}}))){{/container}} 74 +{{/info}} 75 +))) 76 + 77 +((( 78 +{{toc/}} 79 +))) 98 98 {{/container}} 81 +{{/container}}