Skip to Content

Changes for page 214 - System Symphony

Last modified by Carlijn Kokkeler on 2024/04/18 13:06
From version 328.1
edited by Carlijn Kokkeler
on 2024/01/02 10:21
Change comment: There is no comment for this version
To version 334.1
edited by Carlijn Kokkeler
on 2024/01/15 14:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +212 - Failover Fiesta
Content
... ... @@ -3,41 +3,14 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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.
6 +**Hi there, eMagiz developers!** This release...
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 a 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** ==
19 -
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.
22 -
23 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
24 -
25 -//__Missing properties overview__//
26 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
27 -
28 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
29 -
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.
32 -
33 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
34 -
35 35  == **Feedback Items** ==
36 36  
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'.
10 +//__Failover setup__//
11 +New components have been created to support a failover setup. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V2.1.0||target="blank"]]
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
13 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
41 41  
42 42  //__External recipients emailaddress__//
43 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.
... ... @@ -54,8 +54,8 @@
54 54  //__Message throughput__//
55 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 56  
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.
30 +//__Cloud template upgrade incorrect rollback__//
31 +An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
59 59  
60 60  //__Next generation block__//
61 61  Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
... ... @@ -77,7 +77,6 @@
77 77  * Check out the release notes [here]
78 78  * Start thinking about how the license tracker can aid your development
79 79  * Start thinking about major, minor, and patch
80 -* Upgrade to the latest build number
81 81  * Keep making great integrations
82 82  
83 83  Let's stay in touch and till next time!
... ... @@ -85,7 +85,6 @@
85 85  {{info}}
86 86  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
87 87  
88 -~*~* Indicates a next-generation-architecture only feature.
89 89  {{/info}}
90 90  )))
91 91