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 +223 - TBD - Content
-
... ... @@ -1,62 +1,32 @@ 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 - 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. 6 +**Hi there, eMagiz developers!** 20 20 21 -//__Cleanup old images__// 22 - 23 -== **Store Improvements** == 24 - 25 - 26 26 == **Feedback Items** == 9 +//__SwaggerUI default__// 10 +Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown. 27 27 28 -//__Alerting manual pause__// 29 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment. 12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 30 30 31 -//__ Orderingofgraphsin Manage__//32 - Thegraphs in Manageare now ordered accordingtoimportance. This means that runtimestatisticsaresortedby "Process CPU usage"(highestfirst), queue statisticsaresortedby "Messagesinqueue" (highestfirst),andHTTP statisticsaresortedby "Unsuccessfulrequests" (highestfirst).14 +//__SwaggerUI default__// 15 +We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10. 33 33 34 -//__ UTCtimesinGrafana panels__//35 - All GrafanapanelsnowshowUTCtimes,which arenormally usedineMagiz, insteadoflocal(browser)timezones.Thisway,it is easier tomatchgraphs withloggingevents or alerts.17 +//__SFTP sessions__// 18 +Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. 36 36 37 -//__Update flow designer version__// 38 -The framework used in the flow designer has been updated to the latest version. 39 - 40 - 41 - 42 42 == **Bug Fixes** == 43 43 44 -//__Gain the ability again to configure certificates in Deploy Architecture again__// 45 -In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture. 46 - 47 -//__Ensure that differing container configurations deploy the correct configuration__// 48 -When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers. 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. 52 - 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"]] 26 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]] 27 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]] 58 58 59 -== **Key takeaways** ==29 +== **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] 37 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.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}} 47 +{{/info}} 48 +))) 49 + 50 +((( 51 +{{toc/}} 52 +))) 80 80 {{/container}} 54 +{{/container}}