Changes for page 214 - System Symphony
Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 374.1
edited by Carlijn Kokkeler
on 2024/02/12 15:09
on 2024/02/12 15:09
Change comment:
There is no comment for this version
To version 156.1
edited by Carlijn Kokkeler
on 2023/10/10 13:56
on 2023/10/10 13:56
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 14- SystemSymphony1 +206 - Situational Deployment - Content
-
... ... @@ -1,47 +1,54 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In th is release, ...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. 7 7 8 -== ** Feedback Items** ==7 +== **Deployment Plan** == 9 9 10 -//__ Updateflows__//11 - Support for deployingtoon premiseWindows machineshasbeendelivered.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. 12 12 13 -//__ Imageversions__//14 - Thedeletionofreleaseswithdeployed container versionswillnotbe blockedanymore. Automatedreleaseclean up behaviour will alsonotexcludethesereleases from deletion.Images that belongto deleted releaseswill be kept if there areotherreleasesthat would reuse them, otherwise theywillbedeletedogetherwiththe releases.12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 15 15 16 -//__ Addingmultipleattributes__//17 - Itisnowpossibleto addmultipleexistingattributestoanentityat once.15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 18 18 19 -//__Monitoring graphs__// 20 -The monitoring graphs can now show data up to the last 30 days. 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 + 21 21 22 -== **Bug Fixes** == 23 -//__Failover group helptext__// 24 -The helptext of the Group attribute has been improved. 26 +== **Feedback Items** == 25 25 26 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]] 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. 27 27 28 -//__ Failover grouprefresh__//29 - A newstate'Leader(singlenode)'hasbeen addedincasethereisnly onenodeforfailoveretup.Moreover,a refreshbuttonisddedinGrouptabof"Start/StopFlows"screen.31 +//__Ordering of graphs in Manage__// 32 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first). 30 30 31 -[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]] 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. 32 32 33 -//__ Resourcepaths__//34 - Aftermigrating a gateway toGen3,thepathreferencestheeventprocessors wouldbe broken.Thishasbeen fixed.37 +//__Update flow designer version__// 38 +The framework used in the flow designer has been updated to the latest version. 35 35 40 + 41 + 42 +== **Bug Fixes** == 43 + 44 + 36 36 == **Fancy Forum Answers** == 37 37 38 38 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: 39 39 40 -* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 41 -* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 42 -* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 49 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 43 43 44 -== **Key Takeaways** ==51 +== **Key takeaways** == 45 45 46 46 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: 47 47 ... ... @@ -52,6 +52,7 @@ 52 52 * Check out the release notes [here] 53 53 * Start thinking about how the license tracker can aid your development 54 54 * Start thinking about major, minor, and patch 62 +* Upgrade to the latest build number 55 55 * Keep making great integrations 56 56 57 57 Let's stay in touch and till next time! ... ... @@ -59,11 +59,6 @@ 59 59 {{info}} 60 60 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 62 -{{/info}} 63 -))) 64 - 65 -((( 66 -{{toc/}} 67 -))) 70 +~*~* Indicates a next-generation-architecture only feature. 71 +{{/info}})))((({{toc/}}))){{/container}} 68 68 {{/container}} 69 -{{/container}}