Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 153.1
edited by Erik Bakker
on 2023/09/15 15:04
Change comment: There is no comment for this version
To version 299.1
edited by Carlijn Kokkeler
on 2023/12/21 13:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,52 +1,54 @@
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!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
8 +== **TBD** ==
8 8  
9 -As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
10 10  
11 +
11 11  == **Feedback Items** ==
12 12  
13 -//__Improved Validation when migrating to the next-generation architecture__//
14 -To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
14 +//__Runtime overview__//
15 +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.
15 15  
16 -{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
17 17  
18 -//__Improved HTTP Statistics__//
19 -To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
19 +//__Missing properties overview__//
20 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
20 20  
21 -//__Show values on the runtime level in Deploy Architecture__//
22 -We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
22 +ADD FIGURE
23 23  
24 -{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
25 -* JMS - The number of queues in the active release.
26 -* Messaging Container - The number of messaging integrations in the active release.
27 -* Messaging Connector - The number of messaging integrations related to this system in the active release.
28 -* API Gateway Container - The number of operations in the active release.
29 -* Event Streaming Container - The number of event processors in the active release.
24 +//__Broker queue metrics dashboards__//
25 +It is now possible to select the MQTT broker in the queue metrics dashboards.
30 30  
31 -There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
32 -
33 33  == **Bug Fixes** ==
34 34  
35 -//__Gain the ability again to configure certificates in Deploy Architecture again__//
36 -In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
29 +//__Deployment execution error message__//
30 +In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup.
37 37  
38 -//__Ensure that differing container configurations deploy the correct configuration__//
39 -When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
32 +//__Cloud template upgrade unjust rollback__//
33 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
40 40  
41 -//__Remove queurying options in Manage__//
42 -To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
35 +//__Missing log entries__//
36 +We improved crash handling so that log messages clearly show when and why a container failed to start.
43 43  
38 +//__Runtime logging__//
39 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
40 +
44 44  == **Fancy Forum Answers** ==
45 45  
46 46  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:
47 47  
48 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
45 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
46 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
47 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
48 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
49 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
49 49  
51 +
50 50  == **Key takeaways** ==
51 51  
52 52  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:
... ... @@ -67,5 +67,11 @@
67 67  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
68 68  
69 69  ~*~* Indicates a next-generation-architecture only feature.
70 -{{/info}})))((({{toc/}}))){{/container}}
72 +{{/info}}
73 +)))
74 +
75 +(((
76 +{{toc/}}
77 +)))
71 71  {{/container}}
79 +{{/container}}