Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 468.1
edited by Carlijn Kokkeler
on 2024/04/23 11:20
on 2024/04/23 11:20
Change comment:
There is no comment for this version
To version 333.1
edited by Carlijn Kokkeler
on 2024/01/03 10:03
on 2024/01/03 10:03
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 -21 9-CreationCarousel1 +211 - Log Luminary - Content
-
... ... @@ -3,55 +3,70 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** 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, mainly relating to the Deploy and Manage phase. 7 7 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 -== **Feedback Items** == 10 -//__Machine agents__// 11 -We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more HERE. 12 +//__Runtime logging__// 13 +We fixed a bug where no new log messages were showing up, even though they were produced by a container. 12 12 13 -//__ Customwebhook__//14 - Weremovedadeprecatedfunctionality that sends a customwebhookwhenupgrading the environment.Pleasefind outmoreHERE.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. 15 15 16 -//__eMagiz Mendix connector__// 17 -We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 18 +== **Overviews** == 18 18 19 -//__ Improved OpenAPIimport__//20 - Thepath lengthinOpenAPIspec importshasbeenincreasedtoamaximumof300characters.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. 21 21 22 -== **Bug Fixes** == 23 -//__Error handling__// 24 -When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this. 23 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 25 25 26 -//__ Volume mapping passwords__//27 - Passwordsfor networkvolumesarehiddenonthemachine afterdeployment.25 +//__Missing properties overview__// 26 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 28 28 29 -//__Create integration removal__// 30 -When removing an integration from Create, the Create phase is correctly updated as well. 28 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 31 31 32 -//__ Legacystatistics__//33 - Legacypagesare nowcorrectly hidden whenrunningonthecurrent runtimearchitecture.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. 34 34 35 -//__Unused properties__// 36 -Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore. 33 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 37 37 38 -//__Enumeration values__// 39 -Enumeration values for event processors can now be edited in Create. 35 +== **Feedback Items** == 40 40 41 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 37 +//__Breaking changes pop-up__// 38 +The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high. 42 42 43 -//__SFTP sessions__// 44 -SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. Please find out more HERE. 40 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]] 45 45 42 +//__External recipients emailaddress__// 43 +The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users. 44 + 45 +//__Broker queue metrics dashboards__// 46 +It is now possible to select the MQTT broker in the queue metrics dashboards. 47 + 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. 50 + 51 + 52 +== **Bug Fixes** == 53 + 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. 56 + 57 +//__Cloud template upgrade incorrect rollback__// 58 +An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks. 59 + 60 +//__Next generation block__// 61 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 62 + 46 46 == **Fancy Forum Answers** == 47 47 48 48 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: 49 49 50 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 51 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 52 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 67 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]] 53 53 54 -== **Key Takeaways** ==69 +== **Key takeaways** == 55 55 56 56 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: 57 57 ... ... @@ -59,7 +59,7 @@ 59 59 * If you have feedback or ideas for us, talk to the Platypus 60 60 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 61 61 * Clear your browser cache (Ctrl + Shift + Del) 62 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]77 +* Check out the release notes [here] 63 63 * Start thinking about how the license tracker can aid your development 64 64 * Start thinking about major, minor, and patch 65 65 * Keep making great integrations