Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 149.1
edited by Erik Bakker
on 2023/08/29 10:56
Change comment: There is no comment for this version
To version 2.1
edited by eMagiz
on 2022/10/12 10:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -204 - Found It
1 +185 - To determine
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.eMagiz
Content
... ... @@ -2,39 +2,48 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
5 +**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
6 6  
7 -== **Feedback Items** ==
7 +==**Audit trail User Management**==
8 8  
9 -//__Improved check on nested property placeholders__//
10 -To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
9 +
10 +==**Next Generation Monitoring & Alerting engine**==
11 +In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now used State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations. In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach). We have already released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]]
12 +
13 +=== **Improvements** ===
14 +
15 +* Performance Deployment plan
16 +When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
17 +
18 +* Flow Designer updates
19 +We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
20 +
21 +
22 +
23 +
24 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
11 11  
12 -//__Removed outdated properties when deploying on the new generation architecture stack__//
13 -We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before connecting to a Kafka cluster but have become obsolete once you migrate.
26 +
27 +== **Feedback items ** ==
14 14  
15 -{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
29 +We have also solved other feedback items besides the key updates around functionality.
16 16  
17 -//__Improved performance Manage Dashboards__//
18 -We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
31 +//__Set runtime field as first selected field on property level__//
32 +With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well.
19 19  
20 -== **Bug Fixes** ==
34 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
35 +
21 21  
22 -//__Errors with long stack traces or long message histories will now also show in eMagiz__//
23 -We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
24 -
25 -//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
26 -We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
27 -
28 28  == **Fancy Forum Answers** ==
29 29  
30 -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:
39 +As always, a gentle reminder to all 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:
31 31  
32 -* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
33 -* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
41 +* [[Start runtime via a delayed start in a Linux environment?>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
42 +* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
34 34  
35 35  == **Key takeaways** ==
36 36  
37 -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:
46 +Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
38 38  
39 39  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
40 40  * If you have feedback or ideas for us, talk to the Platypus
... ... @@ -45,12 +45,13 @@
45 45  * Start thinking about major, minor, and patch
46 46  * Upgrade to the latest build number
47 47  * Keep making great integrations
57 +* Check out the new documentation portal.
48 48  
49 49  Let's stay in touch and till next time!
50 50  
51 51  {{info}}
52 -~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
62 +~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53 53  
54 -~*~* Indicates a next-generation-architecture only feature.
64 +~*~* Indicates a GEN3-only feature.
55 55  {{/info}})))((({{toc/}}))){{/container}}
56 56  {{/container}}