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 06-SituationalDeployment1 +219 - Creation Carousel - Content
-
... ... @@ -1,54 +1,57 @@ 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!** In thelast fewweeks,wehavedone muchworkfortheDeployphase.On topof that, we have worked onseveral storefunctionalities.Next tothis,wehave severalsmallerfeedbackitemsfromour hackathon effortsthatare now releasedtoyou.6 +**Hi there, eMagiz developers!** This release, we introduce new environment templates for Docker single and double lane. Moreover, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published. 6 6 7 -== **Deployment Plan** == 8 +== **Environment Template R13 Docker - Single Lane** == 9 +This release introduces a new non-service affecting environment template for all our customers running in a single-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Single Lane.WebHome||target="blank"]]. 8 8 9 - //__Improved deployment planto maketheprocess betterandmorepredictable__//10 -Th ealgorithm forgenaratinga default deployment planis improvedtokeep jmsdowntimeandalertingtoa minimum. Next tothis,thestart/stop/restartmachinedeploymentstepsare now also executedcorrectlyforaws andon-premisesmachines.11 +== **Environment Template R15 Docker - Double Lane** == 12 +This release introduces a new non-service affecting environment template for all our customers running in a double-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R15 Docker - Double Lane.WebHome||target="blank"]]. 11 11 12 -//__Editing release properties__// 13 -With this release, it will be possible to change the description of a property by editing the property. 14 +== **Feedback Items** == 14 14 15 -//__ JMSmemory settingcheck__//16 - Achangeinmemorysettingstriggersredeploymentofthecontainer now.16 +//__eMagiz Mendix connector__// 17 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 17 17 18 -//__Properties tab__// 19 -We have removed the deprecated tab Properties in the Deploy phase. 20 - 21 -//__Cleanup old images__// 22 - 23 -== **Store Improvements** == 24 - 19 +//__Improved OpenAPI import__// 20 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 25 25 26 -== **Feedback Items** == 22 +== **Bug Fixes** == 23 +//__Error handling__// 24 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this. 27 27 28 -//__ Alertingmanualpause__//29 - A few releasesagowe changed the behaviorof alerting in thedeployment plan. Now each time when a deployment plan isexecuted the alerting will be automaticallyre-enabledwhenthedeployer closesthe deployment plan or closes theweb browser.The majority of theusers are happy with thenewbehavior, but there are some use cases that you donotwantstart thealerting immediately. Withthis release, if alerting has beenpaused manually, this will not be activated automatically aftera releasedeployment.26 +//__Volume mapping passwords__// 27 +Passwords for network volumes are hidden on the machine after deployment. 30 30 31 -//__ Orderingof graphsinManage__//32 - Thegraphs inManage arenow ordered accordingto importance.This meansthat runtimestatistics are sortedby "ProcessCPU usage"(highestfirst), queue statistics aresorted by "Messagesin queue"(highestfirst), and HTTP statistics are sorted by "Unsuccessfulrequests" (highestfirst).29 +//__Create integration removal__// 30 +When removing an integration from Create, the Create phase is correctly updated as well. 33 33 34 -//__ UTCtimesin Grafana panels__//35 - All Grafanapanels nowshow UTCtimes,which arenormallyusedineMagiz,insteadof local (browser) timezones. This way, itis easiertomatchgraphs with loggingevents oralerts.32 +//__Legacy statistics__// 33 +Legacy pages are now correctly hidden when running on the current runtime architecture. 36 36 37 -//__U pdateflow designer version__//38 - Theframeworkusedintheflowdesignerhasbeen updatedto the latest version.35 +//__Unused properties__// 36 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore. 39 39 38 +//__Enumeration values__// 39 +Enumeration values for event processors can now be edited in Create. 40 40 41 - 42 -== **Bug Fixes** == 41 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 43 43 43 +//__SFTP sessions__// 44 +SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released. 44 44 45 45 == **Fancy Forum Answers** == 46 46 47 47 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: 48 48 49 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 50 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 51 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 52 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 50 50 51 -== **Key takeaways** ==54 +== **Key Takeaways** == 52 52 53 53 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: 54 54 ... ... @@ -56,10 +56,9 @@ 56 56 * If you have feedback or ideas for us, talk to the Platypus 57 57 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 58 58 * Clear your browser cache (Ctrl + Shift + Del) 59 -* Check out the release notes [here] 62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]] 60 60 * Start thinking about how the license tracker can aid your development 61 61 * Start thinking about major, minor, and patch 62 -* Upgrade to the latest build number 63 63 * Keep making great integrations 64 64 65 65 Let's stay in touch and till next time! ... ... @@ -67,6 +67,11 @@ 67 67 {{info}} 68 68 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 69 69 70 -~*~* Indicates a next-generation-architecture only feature. 71 -{{/info}})))((({{toc/}}))){{/container}} 72 +{{/info}} 73 +))) 74 + 75 +((( 76 +{{toc/}} 77 +))) 72 72 {{/container}} 79 +{{/container}}