Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 133.1
edited by Erik Bakker
on 2023/08/01 14:11
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
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,79 +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 crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **Release Properties** ==
8 -As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, timing of changing properties was crucial to avoid costly mistakes on Production. On top of that it was not always clear whether a property value was indeed updated as it was not linked to something that was deployed. These considerations let us to change the property management behavior not only on our next-generation architecture but also on our current generation architecture. Having said that, there are several key changes compared to the current way of managing your properties. Most notably among these are:
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.
9 9  
10 -* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
11 -* Property placeholders (i.e. the names of properties as given in Create) are now automatically created for you. This to avoid mistakes when filling them in.
12 -* When adding or editing a property you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double lane setup or having a distributed landscape of containers.
13 -* A, for most, new concept of a "property release" is introduced. With the help of this functionality you can easily change a property on Production without having to create a completely new release in Test and promote it to the Production environment.
12 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
14 14  
15 -{{info}}For more information please check out the following microlearnings:
14 +//__Missing properties overview__//
15 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
16 16  
17 -* [[Property Management>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18 -* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
19 -* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
20 20  
21 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22 -{{/info}}
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.
23 23  
24 -== ** Manage - Next generation graphs improvements ** ==
25 -As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the manage graphs as we retrieve and show less fine-grained information when zooming out.
22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
24 +//__Missing log entries__//
25 +We improved crash handling so that log messages clearly show when and why a container failed to start.
28 28  
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 29  == **Feedback Items** ==
30 30  
31 -//__Improved editability when testing in eMagiz wihout Edit rights in Create__//
32 -Without having edit rights in the Create phase you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we missed during the implementation. These have been fixed allowing those without edit rights to now also change the name and description of the test case.
33 33  
34 -//__Improved auditability on Deploy Architecture__//
35 -To improve the audtiability on Deploy Architecture we now also log when someone with Admin rights changes specific functions on this level (i.e. Fixed IP).
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  
37 -//__Test your own exported work__//
38 -We have now made it possible to test your own exported work to the Store before it gets approved. This will increase the quality of store items we have, and our partners, have on offer within the store.
36 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
39 39  
40 -{{info}}In case the concept of the store is new for you please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
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.
41 41  
42 -//__Improved Audit Trail on several places__//
43 -In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
41 +//__Broker queue metrics dashboards__//
42 +It is now possible to select the MQTT broker in the queue metrics dashboards.
44 44  
45 -//__Removed the erroneous alert on message mapping when having a passthrough API__//
46 -This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
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.
47 47  
47 +
48 48  == **Bug Fixes** ==
49 49  
50 -//__Avoid clicking on other components while deleting another__//
51 -To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
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 52  
53 -//__Improved validation feedback in migrating to the next-generation architecture__//
54 -We have improved the validation feedback when migrating to the next-generation architecture.
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 55  
56 -//__Make sure that user credentials can be viewed with view rights__//
57 -This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
56 +//__Next generation block__//
57 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
58 58  
59 -//__Refresh behavior within the deployment plan is fixed__//
60 -This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
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 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:
65 65  
66 -* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
67 -* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
68 -* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||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"]]
69 69  
72 +
70 70  == **Key takeaways** ==
71 71  
72 -Thanks to all that helped 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:
73 73  
74 74  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75 75  * If you have feedback or ideas for us, talk to the Platypus
76 -* 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.
77 77  * Clear your browser cache (Ctrl + Shift + Del)
78 78  * Check out the release notes [here]
79 79  * Start thinking about how the license tracker can aid your development
... ... @@ -86,6 +86,12 @@
86 86  {{info}}
87 87  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
88 88  
89 -~*~* Indicates a GEN3-only feature.
90 -{{/info}})))((({{toc/}}))){{/container}}
92 +~*~* Indicates a next-generation-architecture only feature.
93 +{{/info}}
94 +)))
95 +
96 +(((
97 +{{toc/}}
98 +)))
91 91  {{/container}}
100 +{{/container}}