Changes for page 206 - Situational Deployment
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 162.1
edited by Carlijn Kokkeler
on 2023/10/11 10:51
on 2023/10/11 10:51
Change comment:
There is no comment for this version
To version 91.1
edited by Erik Bakker
on 2023/03/14 06:52
on 2023/03/14 06:52
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-SituationalDeployment1 +194 - Big Leap - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -2,98 +2,74 @@ 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 fewweeks, we have donemuchworkfor theDeployphase.Ontop ofthat,we haveworked on severalstorefunctionalities.Nextto this,wehave severalsmaller feedbackitemsfromourhackathoneffortsthat arenowreleasedtoyou.5 +**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements. 6 6 7 -== ** DeploymentPlan** ==7 +== **3rd generation improvements** == 8 8 9 -//__ Improveddeploymentplantomaketheprocessbetter and morepredictable__//10 - The algorithmfor genaratinga default deploymentplanisimprovedtokeepjmsdowntimeandalertingtoaminimum.Nexttothis,thestart/stop/restartmachinedeployment steps are nowalso executedcorrectlyforawsandon-premisesmachines.9 +//__Better feedback in error log when a corrupt stylesheet is encountered__// 10 +We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action. 11 11 12 -//__ Editingrelease properties__//13 -W ith thisrelease,itwillbepossible tochangethedescription of apropertyby editingtheproperty.12 +//__Better internal error handling to avoid unnecessary alerting and notifications__// 13 +We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack. 14 14 15 -//__ JMSmemory settingcheck__//16 - A change inmemory settings triggers redeploymentofthecontainernow.15 +//__Improved Manage Dashboard__// 16 +This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture. 17 17 18 -//__ Properties tab__//19 -We have removedthe deprecatedtabPropertiesin theDeployphase.18 +//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__// 19 +When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes. 20 20 21 -//__ Cleanup oldimages__//22 -Wh enareleaseisremoved,the relatedunusedimagesinthe on-premisesmachineswillberemoved as well.21 +//__Improved process of deploy preparation__// 22 +With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced. 23 23 24 -//__ Performance improvements forloadingreleases__//25 - Performanceimprovementshavebeenimplementedforloadingreleases inDeploy.Releasesshouldnowloadfasterthanbefore.Allfunctionalityshouldremain exactlythesameasbefore.24 +//__Improved migration of Streaming container__// 25 +When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention. 26 26 27 -== **Store Improvements** == 27 +//__Add History to Notifications in Manage__// 28 +To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications. 28 28 29 -//__ Messagedefinitionelementsorder__//30 - We fixedsuethat theorderofmessagedefinitionelements waschangedafterbeingimported.30 +//__Improved Manage phase for Event Streaming__// 31 +Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you. 31 31 32 -//__Impro tinga storeitem withsynchronousmessage definitions__//33 -W efixedan issuethatimporting a storeitemwithsynchronous messagedefinitionswentg.Now,the importedmessagedefinitions should correspondwiththe exportedmessage definitions.33 +//__Improved help text for network volumes__// 34 +With this release we have improved the help text that explains network volumes and how to use them within our solution. 34 34 35 -//__Importing store itmes containing static copies__// 36 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly. 36 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}} 37 37 38 -== **Feedback Items** ==38 +== **Feedback items ** == 39 39 40 -//__ Alertingmanualpause__//41 - Afewreleasesagowechangedthe behaviorof alerting in the deployment plan. Noweachtime whenadeploymentplanisexecuted the alertingwill be automatically re-enabled when the deployer closes the deploymentplan or closestheweb browser. The majority of the usersare happy with thenew behavior, butthere are someusecases that youdonotwantstartthealerting immediately.With thiselease, if alerting has been pausedmanually, this will not beactivated automaticallyaftera release deployment.40 +//__Removed OData as option for an API Gateway operation__// 41 +With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform. 42 42 43 -//__ Orderingofgraphs inManage__//44 - Thegraphs inManageare now orderedaccordingtoimportance.This meansthat runtimestatistics aresortedby "ProcessCPU usage"(highestfirst),queuestatisticsaresortedby "Messagesinqueue" (highestfirst), andHTTP statistics are sortedby "Unsuccessfulrequests"(highestfirst).43 +//__Changes in API Gateway operation paths is automatically updated in Create__// 44 +When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry. 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. 46 +{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}} 48 48 49 -//__Update flow designer version__// 50 -The framework used in the flow designer has been updated to the latest version. 48 +== **Bug fixes ** == 51 51 52 -//__ CarwashtrackTLS versions in logging__//53 - Anewloggingfeature willbe released,enablingus tomakebetter choices in deprecatingoldencryptionstandards.50 +//__Prevent endless loop in Deploy -> User Management__// 51 +With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion. 54 54 55 -//__Moving channels in the flow designer__// 56 -Moving already attached channels in the flow designer has been made sligthly easier. 53 +{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}} 57 57 58 -//__ Topicsizesdescriptionchange__//59 - In thechangedescription(andHistory)whenalteringthe topicsizeofa topicthenew andold valuewere switchedaroundcreatingconfusion,this has been resolved.55 +//__Update error handling during migration to the 3rd generation runtime__// 56 +As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration. 60 60 61 -//__Password change notification__// 62 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action. 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. 66 - 67 -//__Inactive user alerting__// 68 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 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 -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"]] 62 +* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]] 63 +* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]] 64 +* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]] 89 89 90 90 == **Key takeaways** == 91 91 92 -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:68 +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: 93 93 94 94 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 95 95 * If you have feedback or ideas for us, talk to the Platypus 96 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 72 +* 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 98 * Check out the release notes [here] 99 99 * Start thinking about how the license tracker can aid your development ... ... @@ -106,6 +106,6 @@ 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.85 +~*~* Indicates a GEN3-only feature. 110 110 {{/info}})))((({{toc/}}))){{/container}} 111 111 {{/container}}