Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
on 2023/06/05 14:27
Change comment:
There is no comment for this version
To version 318.1
edited by Carlijn Kokkeler
on 2023/12/21 14:49
on 2023/12/21 14:49
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 -1 99-HomeImprovements1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,53 +1,82 @@ 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 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 +**Hi there, eMagiz developers!** 6 6 7 -== **Next generation improvements and bug fixes** == 8 +== **Overviews and logging** == 9 +//__Runtime overview__// 10 +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. 8 8 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. 12 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 11 11 12 -//__ Reasonwhyruntime cannot starts now in thevastmajority of cases reported back__//13 - In this release,we haveimprovedthe waywereportfailuresduringstartupofruntimes.Thiswillensure thatit becomesmuch easier topinpoint what went wrongupon startup.14 +//__Missing properties overview__// 15 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 14 14 15 - {{info}}Note that this fix is part of a new runtime imagefor the next-generationruntimes.Thereleasenotes of this canbe found [[here>>doc:Main.ReleaseInformation.RuntimeImages.WebHome||target="blank"]]{{/info}}17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 16 16 17 -//__ Forcedcongestioncontrol__//18 - Toduce thenumberofrepeatingmails within a10 minutewindowwe have nowforcedcongestion controlonallalertsgeneratedviatheplatform.19 +//__Runtime restart or redeploy overview__// 20 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 19 19 22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 20 20 21 -//__ Improved validation errorson theinvalidconfigurationof HTTP outbound components__//22 - This releasefixes andre-introducestheoptiontoexecute youractionsontheeMagiz perzoneorallatoncewhenrunninginadouble-laneDockersetup.24 +//__Missing log entries__// 25 +We improved crash handling so that log messages clearly show when and why a container failed to start. 23 23 24 -//__Improved migration behavior__// 25 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are: 26 -A smoother migration of your JMS (and backup JMS) process. 27 -Shortening of names that otherwise would be too long, additional feedback given to the user. 28 -Feedback when the migration process is finished. 27 +//__Runtime logging__// 28 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 29 29 30 -//__Additional checks when deploying__// 31 -This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other. 30 +== **Feedback Items** == 32 32 33 -== **Store Improvements** == 34 34 35 -== **Event Streaming - Certificate Management** == 33 +//__Breaking changes pop-up__// 34 +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'. 36 36 36 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 37 + 38 +//__External recipients emailaddress__// 39 +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. 40 + 41 +//__Broker queue metrics dashboards__// 42 +It is now possible to select the MQTT broker in the queue metrics dashboards. 43 + 44 +//__Runtime image version__// 45 +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. 46 + 47 + 48 +== **Bug Fixes** == 49 + 50 +//__Message throughput__// 51 +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. 52 + 53 +//__Cloud template upgrade unjust rollback__// 54 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks. 55 + 56 +//__Next generation block__// 57 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 58 + 59 +//__Deployment execution error message__// 60 +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. 61 + 37 37 == **Fancy Forum Answers** == 38 38 39 39 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: 40 40 41 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]] 42 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]] 66 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 67 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 68 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 69 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 70 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 43 43 72 + 44 44 == **Key takeaways** == 45 45 46 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:75 +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 48 48 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 49 49 * If you have feedback or ideas for us, talk to the Platypus 50 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 79 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 51 51 * Clear your browser cache (Ctrl + Shift + Del) 52 52 * Check out the release notes [here] 53 53 * Start thinking about how the license tracker can aid your development ... ... @@ -60,6 +60,12 @@ 60 60 {{info}} 61 61 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 62 62 63 -~*~* Indicates a GEN3-only feature. 64 -{{/info}})))((({{toc/}}))){{/container}} 92 +~*~* Indicates a next-generation-architecture only feature. 93 +{{/info}} 94 +))) 95 + 96 +((( 97 +{{toc/}} 98 +))) 65 65 {{/container}} 100 +{{/container}}