Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From 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
To version 320.1
edited by Carlijn Kokkeler
on 2023/12/21 14:51
on 2023/12/21 14:51
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -5,7 +5,17 @@ 5 5 6 6 **Hi there, eMagiz developers!** 7 7 8 -== **Overviews and logging** == 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. 11 + 12 +//__Runtime logging__// 13 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 14 + 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. 17 + 18 +== **Overviews** == 9 9 //__Runtime overview__// 10 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. 11 11 ... ... @@ -21,12 +21,7 @@ 21 21 22 22 [[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 23 23 24 -//__Missing log entries__// 25 -We improved crash handling so that log messages clearly show when and why a container failed to start. 26 26 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 - 30 30 == **Feedback Items** == 31 31 32 32 ... ... @@ -56,9 +56,6 @@ 56 56 //__Next generation block__// 57 57 Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 58 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 - 62 62 == **Fancy Forum Answers** == 63 63 64 64 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: