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,93 +1,59 @@ 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 lastfew weeks, we havedonemuch workfor theDeployphase.On topofthat, we haveworkedon several storefunctionalities.Nextto this,we haveseveralsmaller feedbackitems from ourhackathon effortsthatarenowreleasedto you.6 +**Hi there, eMagiz developers!** This release, 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 - 9 -//__Improved deployment plan to make the process better and more predictable__// 10 -The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines. 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 - 15 -//__JMS memory setting check__// 16 -A change in memory settings triggers redeployment of the container now. 17 - 18 -//__Properties tab__// 19 -We have removed the deprecated tab Properties in the Deploy phase. 20 - 21 -//__Cleanup old images__// 22 -When a release is removed, the related unused images in the on-premises machines will be removed as well. 23 - 24 -//__Performance improvements for loading releases__// 25 -Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before. 26 - 27 -== **Store Improvements** == 28 - 29 -//__Message definition elements order__// 30 -We fixed an issue that the order of message definition elements was changed after being imported. 31 - 32 -//__Improting a store item with synchronous message definitions__// 33 -We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions. 34 - 35 -//__Importing store items containing static copies__// 36 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly. 37 - 38 38 == **Feedback Items** == 39 39 40 -//__ Alertingmanualpause__//41 - 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.10 +//__eMagiz Mendix connector__// 11 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 42 42 43 -//__ Orderingof graphs in Manage__//44 -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).13 +//__Improved OpenAPI import__// 14 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 45 45 46 -//__ UTCtimesinGrafana panels__//47 - All Grafanapanelsnowshow UTCtimes,which arenormallyusedineMagiz,insteadoflocal (browser)timezones.Thisway,itiseasiertomatchgraphswith loggingevents oralerts.16 +//__Flow test stack trace__// 17 +If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab. 48 48 49 -//__Update flow designer version__// 50 -The framework used in the flow designer has been updated to the latest version. 19 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]] 51 51 52 -//__Carwash track TLS versions in logging__// 53 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 21 +{{info}}TBD{{/info}} 54 54 55 -//__Moving channels in the flow designer__// 56 -Moving already attached channels in the flow designer has been made sligthly easier. 57 57 58 -//__Topic sizes description change__// 59 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved. 24 +== **Bug Fixes** == 25 +//__Error handling__// 26 +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. 60 60 61 -//__ Passwordchangenotification__//62 - Whenan account passwordchangerequestis made,even when this fails, a mail is sentto the account ownerto informtheownerabout theaction.28 +//__Volume mapping passwords__// 29 +Passwords for network volumes are hidden on the machine after deployment. 63 63 64 -//__ Password comparison__//65 -When changing apassword,itiscompared toalistof known databasebreachesforsecurity.A warning isshownwhen the passwordcorresponds withapasswordin the database.31 +//__Create integration removal__// 32 +When removing an integration from Create, the Create phase is now correctly updated. 66 66 67 -//__ Inactiveuseralerting__//68 - Inactivated usersare nowremoved from all alert settings(included“disabled“settings)toavoidundesirable notifications.34 +//__Legacy statistics__// 35 +Legacy pages are now correctly hidden when running on the current runtime architecture. 69 69 70 -//__ Alphabetical sorting onuserlevel in HTTP statistics__//71 - Variablesinthe3rdgenerationruntimesHTTPstatisticsdetailpagesarenow sortedcaseinsensitive.37 +//__Unused properties__// 38 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore. 72 72 73 -== **Bug Fixes** == 40 +//__Enumeration values__// 41 +Enumeration values for event processors can now be edited in Create. 74 74 75 -//__Flow designer styling__// 76 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities. 43 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 77 77 78 -//__P artialsearch for messages__//79 - Itis nowpossible to searchonmessages partially inManageMonitoring.Forexample,search forUptimecanbedonebysearching for"up" "time""ptim".45 +//__SFTP sessions__// 46 +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. 80 80 81 -//__Disk usage after cloud template update__// 82 -Several accounts showed significantly more disk usage after the last cloud template update, this has been resolved. 83 - 84 84 == **Fancy Forum Answers** == 85 85 86 86 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: 87 87 88 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 52 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 53 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 54 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 89 89 90 -== **Key takeaways** ==56 +== **Key Takeaways** == 91 91 92 92 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: 93 93 ... ... @@ -95,10 +95,9 @@ 95 95 * If you have feedback or ideas for us, talk to the Platypus 96 96 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 97 97 * Clear your browser cache (Ctrl + Shift + Del) 98 -* Check out the release notes [here] 64 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 99 99 * Start thinking about how the license tracker can aid your development 100 100 * Start thinking about major, minor, and patch 101 -* Upgrade to the latest build number 102 102 * Keep making great integrations 103 103 104 104 Let's stay in touch and till next time! ... ... @@ -106,6 +106,11 @@ 106 106 {{info}} 107 107 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 108 108 109 -~*~* Indicates a next-generation-architecture only feature. 110 -{{/info}})))((({{toc/}}))){{/container}} 74 +{{/info}} 75 +))) 76 + 77 +((( 78 +{{toc/}} 79 +))) 111 111 {{/container}} 81 +{{/container}}