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,62 +1,61 @@ 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 the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.6 +**Hi there, eMagiz developers!** 6 6 7 -== **Deployment Plan** == 8 +== **Environment Template R13 Docker - Single Lane** == 9 +TBD 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"]]. 8 8 9 - //__Improved deployment planto maketheprocess betterandmorepredictable__//10 -Th ealgorithm forgenaratinga defaultdeploymentplanis improvedtokeep jmsdowntimeandalerting toa minimum.Next tothis,thestart/stop/restart machinedeploymentstepsare now also executedcorrectlyforaws andon-premisesmachines.11 +== **Environment Template R15 Docker - Double Lane** == 12 +TBD 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"]]. 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 14 15 -//__JMS memory setting check__// 16 -A change in memory settings triggers redeployment of the container now. 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 - 25 - 26 26 == **Feedback Items** == 17 +//__Machine agents__// 18 +We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more HERE. 27 27 28 -//__ Alertingmanualpause__//29 - A fewreleasesagowe changedthe behavior of alertingin the deploymentplan. Noweach timewhenadeployment planisexecutedthealertingwillbe automatically re-enabled when the deployer closes the deployment plan orclosestheweb browser. The majorityof theusersare happy with the new behavior, but there are some use cases that you donotwantstart the alerting immediately.Withthis release, if alertinghas been paused manually, this will not be activated automatically aftera release deployment.20 +//__eMagiz Mendix connector__// 21 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 30 30 31 -//__ Orderingof graphs in Manage__//32 -The graphsinManagearenowordered accordingtoimportance. Thismeans that runtimestatisticsare sortedby "Process CPU usage"(highest first), queue statistics aresortedby "Messagesin queue"(highestfirst),andHTTP statisticsare sorted by "Unsuccessful requests" (highest first).23 +//__Improved OpenAPI import__// 24 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 33 33 34 -//__UTC times in Grafana panels__// 35 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts. 26 +== **Bug Fixes** == 27 +//__Error handling__// 28 +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. 36 36 37 -//__ Update flow designerversion__//38 - The framework usedin theflowdesignerhasbeenupdatedto thelatestversion.30 +//__Volume mapping passwords__// 31 +Passwords for network volumes are hidden on the machine after deployment. 39 39 33 +//__Create integration removal__// 34 +When removing an integration from Create, the Create phase is correctly updated as well. 40 40 41 - 42 - ==**BugFixes**==36 +//__Legacy statistics__// 37 +Legacy pages are now correctly hidden when running on the current runtime architecture. 43 43 44 -//__ Gaintheability again to configurecertificatesin Deploy Architecture again__//45 - In restrictingtheconfiguration optionsonthecertificatelevel inone of ourlatter releases,it becameimpossiblefornormal userstoadd andeditcertificateswithin DeployArchitecture. To resolvethisproblemwehave nowreleased a fixto resolvethis issue,givingpeoplethe abilityagain toadd andedit certificatesunder DeployArchitecture.39 +//__Unused properties__// 40 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore. 46 46 47 -//__En surethat differing container configurationsdeploy the correct configuration__//48 - Whenyourun in amulti-runtimeconfiguration and changethe actualflowsthat needtorunoncontainerA vs.containerB, it happened before that all flowswere stillbeingdeployedon all runtimes. With this release, we will feedthis informationcorrectly to our infrastructureto ensure the correct and configured flows are deployed on the proper containers.42 +//__Enumeration values__// 43 +Enumeration values for event processors can now be edited in Create. 49 49 50 -//__Remove queurying options in Manage__// 51 -To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors. 45 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 52 52 47 +//__SFTP sessions__// 48 +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. Please find out more HERE. 49 + 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 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 54 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 55 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 56 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 58 58 59 -== **Key takeaways** ==58 +== **Key Takeaways** == 60 60 61 61 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: 62 62 ... ... @@ -64,10 +64,9 @@ 64 64 * If you have feedback or ideas for us, talk to the Platypus 65 65 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 66 66 * Clear your browser cache (Ctrl + Shift + Del) 67 -* Check out the release notes [here] 66 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]] 68 68 * Start thinking about how the license tracker can aid your development 69 69 * Start thinking about major, minor, and patch 70 -* Upgrade to the latest build number 71 71 * Keep making great integrations 72 72 73 73 Let's stay in touch and till next time! ... ... @@ -75,6 +75,11 @@ 75 75 {{info}} 76 76 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 77 77 78 -~*~* Indicates a next-generation-architecture only feature. 79 -{{/info}})))((({{toc/}}))){{/container}} 76 +{{/info}} 77 +))) 78 + 79 +((( 80 +{{toc/}} 81 +))) 80 80 {{/container}} 83 +{{/container}}