Changes for page 207 - Aligned State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 157.1
edited by Carlijn Kokkeler
on 2023/10/10 14:06
on 2023/10/10 14:06
Change comment:
There is no comment for this version
To version 123.1
edited by Erik Bakker
on 2023/06/08 08:11
on 2023/06/08 08:11
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 206-Situational Deployment1 +199 - Home Improvements - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -2,69 +2,51 @@ 2 2 {{container layoutStyle="columns"}}((( 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 donemuchworkfortheDeployphase.Ontop ofthat,we haveworked onseveralstore functionalities.Nextto this,we haveseveralsmallerfeedbackitemsfromourhackathonefforts that are nowreleasedto you.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern. 6 6 7 -== ** DeploymentPlan** ==7 +== **Next generation improvements and bug fixes** == 8 8 9 -//__ Improveddeploymentplan tomaketheprocessbetterand more predictable__//10 - Thealgorithmforgenaratingadefault deploymentplanis improvedtokeepjmsdowntime andalertingtoaminimum.Nexttothis,the start/stop/restartmachinedeploymentsteps are nowalso executedcorrectlyfor aws andon-premisesmachines.9 +//__Enhanced overview of the HTTP Statistics__// 10 +As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort. 11 11 12 -//__ Editingreleaseproperties__//13 - Withthis release, it willbe possible tochangethedescriptionofapropertyby editingtheproperty.12 +//__Reason why runtime cannot start is now in the vast majority of cases reported back__// 13 +In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup. 14 14 15 -//__JMS memory setting check__// 16 -A change in memory settings triggers redeployment of the container now. 15 +{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 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. 17 +//__Forced congestion control__// 18 +To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform. 23 23 20 +//__Unused images are cleaned up__// 21 +This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan. 22 + 24 24 == **Store Improvements** == 25 - 26 26 27 -== **Feedback Items** == 25 +//__Improved importing behavior for specific use cases__// 26 +Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users. 28 28 29 -//__ Alerting manualpause__//30 - A few releases ago we changedthebehaviorof alerting in the deployment plan. Noweach time when a deployment plan isexecuted the alerting willbe automatically re-enabledwhenthe deployercloses the deployment plan orclosestheweb browser. The majorityof theusersrehappy withthenewbehavior, buttherearesome use cases thatyou do not wantstart thealerting immediately. With thisrelease, ifalertinghas beenpausedmanually,this will not beactivated automatically aftera release deployment.28 +//__Fixed bug in creating a message mapping on top of an imported system message__// 29 +It is now possbile to create a message mapping to an imported system message from the store. 31 31 32 -//__Ordering of graphs in Manage__// 33 -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). 31 +== **Event Streaming - Certificate Management** == 34 34 35 -//__ UTC timesin Grafanapanels__//36 -A llGrafanapanels nowshowUTCtimes,whichare normally usedineMagiz,insteadoflocal(browser)timezones. This way,itiseasiertomatchgraphs withlogging events or33 +//__Expired certification notification__// 34 +As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 37 37 38 -//__Update flow designer version__// 39 -The framework used in the flow designer has been updated to the latest version. 40 - 41 -//__Carwash track TLS versions in logging__// 42 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 43 - 44 -//__Moving channels in the flow designer__// 45 -Moving already attached channels in the flow designer has been made sligthly easier. 46 - 47 -//__Topic sizes description change__// 48 -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. 49 - 50 - 51 - 52 -== **Bug Fixes** == 53 - 54 - 55 55 == **Fancy Forum Answers** == 56 56 57 57 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: 58 58 59 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 40 +* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]] 41 +* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]] 60 60 61 61 == **Key takeaways** == 62 62 63 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:45 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 64 64 65 65 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 66 66 * If you have feedback or ideas for us, talk to the Platypus 67 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 49 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 68 68 * Clear your browser cache (Ctrl + Shift + Del) 69 69 * Check out the release notes [here] 70 70 * Start thinking about how the license tracker can aid your development ... ... @@ -77,6 +77,6 @@ 77 77 {{info}} 78 78 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 79 79 80 -~*~* Indicates a next-generation-architecture only feature.62 +~*~* Indicates a GEN3-only feature. 81 81 {{/info}})))((({{toc/}}))){{/container}} 82 82 {{/container}}