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,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 -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** == 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. 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.20 +//__eMagiz Mendix connector__// 21 +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).23 +//__Improved OpenAPI import__// 24 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 45 45 46 -//__UTC times in Grafana panels__// 47 -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. 48 48 49 -//__ Update flow designerversion__//50 - The framework usedin theflowdesignerhasbeenupdatedto thelatestversion.30 +//__Volume mapping passwords__// 31 +Passwords for network volumes are hidden on the machine after deployment. 51 51 52 -//__C arwashtrackTLS versionsin logging__//53 - A newloggingfeaturewillbereleased,enabling usto makebetterchoices indeprecating old encryptionstandards.33 +//__Create integration removal__// 34 +When removing an integration from Create, the Create phase is correctly updated as well. 54 54 55 -//__ Movingchannelsinthe flow designer__//56 - Movingalready attachedchannelsin theflowdesignerhasbeen madesligthlyeasier.36 +//__Legacy statistics__// 37 +Legacy pages are now correctly hidden when running on the current runtime architecture. 57 57 58 -//__ Topicsizesdescription change__//59 - In thechangedescription(andHistory)when alteringthetopic size ofa topicthenew andoldvaluewereswitchedaroundcreatingconfusion,this has beenresolved.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. 60 60 61 -//__ Password changenotification__//62 - Whenan account password changerequestismade, evenwhen thisfails, a mail issent to the accountownertoinformtheownerabout theaction.42 +//__Enumeration values__// 43 +Enumeration values for event processors can now be edited in Create. 63 63 64 -//__Password comparison__// 65 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database. 45 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 66 66 67 -//__ Inactiveuser alerting__//68 - Inactivatedusersarenow removedfromallalert settings(included“disabled“settings)toavoidundesirablenotifications.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. 69 69 70 -//__Alphabetical sorting on user level in HTTP statistics__// 71 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 72 - 73 -== **Bug Fixes** == 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. 77 - 78 -//__Partial search for messages__// 79 -It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim". 80 - 81 -//__Disk usage after cloud template update__// 82 -In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates. 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"]] 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"]] 89 89 90 -== **Key takeaways** ==58 +== **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] 66 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.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}} 76 +{{/info}} 77 +))) 78 + 79 +((( 80 +{{toc/}} 81 +))) 111 111 {{/container}} 83 +{{/container}}