Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 320.1
edited by Carlijn Kokkeler
on 2023/12/21 14:51
Change comment: There is no comment for this version
To version 318.1
edited by Carlijn Kokkeler
on 2023/12/21 14:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,17 +5,7 @@
5 5  
6 6  **Hi there, eMagiz developers!**
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.
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** ==
8 +== **Overviews and logging** ==
19 19  //__Runtime overview__//
20 20  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.
21 21  
... ... @@ -31,7 +31,12 @@
31 31  
32 32  [[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
33 33  
24 +//__Missing log entries__//
25 +We improved crash handling so that log messages clearly show when and why a container failed to start.
34 34  
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 +
35 35  == **Feedback Items** ==
36 36  
37 37  
... ... @@ -61,6 +61,9 @@
61 61  //__Next generation block__//
62 62  Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
63 63  
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 +
64 64  == **Fancy Forum Answers** ==
65 65  
66 66  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: