Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 171.1
edited by Carlijn Kokkeler
on 2023/10/11 15:54
on 2023/10/11 15:54
Change comment:
There is no comment for this version
To version 322.1
edited by Carlijn Kokkeler
on 2023/12/21 15:09
on 2023/12/21 15:09
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 06-Situational Deployment1 +211 - Log Luminary - Content
-
... ... @@ -1,104 +1,76 @@ 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 th e lastfew weeks, we have done much workfortheDeployphase.Ontopofthat, wehaveworkedon severalstorefunctionalities. Next to this, we have severalsmaller feedbackitems from ourhackathonffortsthat arenow releasedto you.6 +**Hi there, eMagiz developers!** In this release, we have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes. 6 6 7 -== **Deployment Plan** == 8 +== **Logging** == 9 +//__Missing log entries__// 10 +We improved crash handling so that log messages clearly show when and why a container failed to start. 8 8 9 -//__ Improved deploymentplan tomakethe process better and more predictable__//10 - Thealgorithmfor genaratingadefaultdeploymentplanis improvedtokeep jmsdowntimeand alertingtoa minimum.Nexttothis,thestart/stop/restart machinedeployment steps are now also executedcorrectlyforaws andon-premises machines.12 +//__Runtime logging__// 13 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 11 11 12 -//__ Editing releaseproperties__//13 - Withthisrelease,itwillbepossibletochange the descriptionofapropertyby editingtheproperty.15 +//__Deployment execution error message__// 16 +In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up. 14 14 15 -//__JMS memory setting check__// 16 -A change in memory settings triggers redeployment of the container now. 18 +== **Overviews** == 17 17 18 -//__ Properties tab__//19 -We haveremovedthedeprecated tabProperties intheDeployphase.20 +//__Runtime overview__// 21 +We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview. 20 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 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 23 23 24 -//__ Performanceimprovementsforloading releases__//25 - Performanceimprovementshave beenimplementedforloading releases in Deploy.Releasesshouldnow load fasterthanbefore.All functionalityshouldremain exactlythe sameasbefore.25 +//__Missing properties overview__// 26 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 26 26 27 - ==**StoreImprovements** ==28 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 28 28 29 -//__ Message definition elements order__//30 - Weixedan issuehattheorderofmessagedefinitionelements waschangedafterbeingimported.30 +//__Runtime restart or redeploy overview__// 31 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 31 31 32 -//__Importing 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. 33 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 34 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 -//__Importing Store content__// 39 -We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store. 40 - 41 -//__Store disclaimer__// 42 -Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer. 43 - 44 44 == **Feedback Items** == 45 45 46 -//__ Alertingmanualpause__//47 - A few releases agowechangedthebehavior of alertingin the deployment plan.Now eachtime whena deployment planisexecuted the alerting will beautomaticallyre-enabledwhenthe deployercloses the deploymentplanorclosesthe webbrowser.The majorityoftheusers are happywith the new behavior, butthereare some use casesthatyou do not want start thelertingimmediately. With thisrelease,if alertinghas beenpaused manually,this will notbeactivated automatically aftera release deployment.37 +//__Breaking changes pop-up__// 38 +Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'. 48 48 49 -//__Ordering of graphs in Manage__// 50 -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). 40 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 51 51 52 -//__ UTCtimes in Grafana panels__//53 - AllGrafana panelsnowshowUTCtimes,whicharenormally usedineMagiz, instead oflocal(browser)timezones. Thisway, it iseasierto matchgraphswithloggingeventsor alerts.42 +//__External recipients emailaddress__// 43 +The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users. 54 54 55 -//__ Updateflow designerversion__//56 - Theframework usedinthe flowdesignerhasbeenupdatedto thelatestversion.45 +//__Broker queue metrics dashboards__// 46 +It is now possible to select the MQTT broker in the queue metrics dashboards. 57 57 58 -//__ CarwashtrackTLSversions in logging__//59 - A newloggingfeaturewillbe released,enabling usto make betterchoicesindeprecatingold encryptionstandards.48 +//__Runtime image version__// 49 +The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment. 60 60 61 -//__Moving channels in the flow designer__// 62 -Moving already attached channels in the flow designer has been made sligthly easier. 63 63 64 -//__Topic sizes description change__// 65 -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. 66 - 67 -//__Password change notification__// 68 -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. 69 - 70 -//__Password comparison__// 71 -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. 72 - 73 -//__Inactive user alerting__// 74 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 75 - 76 -//__Alphabetical sorting on user level in HTTP statistics__// 77 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 78 - 79 -//__SOAP Web services path__// 80 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings. 81 - 82 82 == **Bug Fixes** == 83 83 84 -//__ Flow designerstyling__//85 -The s tyling oftheflowdesigner'sleft componentpanel hasbeen restructured,solvinga rarebug which wouldbreakthestylingofcertainfunctionalities.54 +//__Message throughput__// 55 +The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases. 86 86 87 -//__ Partialsearchformessages__//88 - Itisnow possibleto searchonmessagespartiallyin ManageMonitoring.Forexample,asearchforUptime canbedone by searchingfor "up""time""ptim".57 +//__Cloud template upgrade unjust rollback__// 58 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks. 89 89 90 -//__ Diskusageaftercloud templateupdate__//91 - In the last cloud templateupdatetherewas an issuewithdisk performance.This has been resolvedin thisrelease. You can manuallyupgradeyourcloudtemplate,orrelyonautomatic updates.60 +//__Next generation block__// 61 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 92 92 93 -//__Error handling migration__// 94 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. 95 - 96 96 == **Fancy Forum Answers** == 97 97 98 98 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: 99 99 100 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 67 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 68 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 69 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 70 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 71 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 101 101 73 + 102 102 == **Key takeaways** == 103 103 104 104 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: ... ... @@ -119,5 +119,11 @@ 119 119 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 120 120 121 121 ~*~* Indicates a next-generation-architecture only feature. 122 -{{/info}})))((({{toc/}}))){{/container}} 94 +{{/info}} 95 +))) 96 + 97 +((( 98 +{{toc/}} 99 +))) 123 123 {{/container}} 101 +{{/container}}