Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 151.1
edited by Erik Bakker
on 2023/09/13 07:02
Change comment: There is no comment for this version
To version 278.1
edited by Carlijn Kokkeler
on 2023/12/04 14:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +209 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,60 +1,56 @@
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!** We have...
6 6  
7 -== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
8 +== **Release Maintenance** ==
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 -== **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.
15 15  
16 -{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
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.
14 +== **Feedback Items** ==
20 20  
21 -//__"Topic Full" alert restriction changed__//
22 -With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better.
16 +//__Container version overview__//
17 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
23 23  
24 -//__Improved performance Manage Dashboards__//
25 -We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
19 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
26 26  
27 -//__Show values on the runtime level in Deploy Architecture__//
28 -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.
21 +//__Unchanged containers__//
22 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
29 29  
30 -{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
31 -* JMS - The number of queues in the active release.
32 -* Messaging Container - The number of messaging integrations in the active release.
33 -* Messaging Connector - The number of messaging integrations related to this system in the active release.
34 -* API Gateway Container - The number of operations in the active release.
35 -* Event Streaming Container - The number of event processors in the active release.
24 +//__Rebuilding of images__//
25 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
36 36  
37 -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}}
38 38  
39 39  == **Bug Fixes** ==
40 40  
41 -//__Improved information Queue Statistics__//
42 -Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release.
30 +//__Runtime metrics processing__//
31 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
43 43  
44 -//__Gain the ability again to configure certificates in Deploy Architecture again__//
45 -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.
33 +//__Deployment plan__//
34 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
46 46  
47 -//__Ensure that differing container configurations deploy the correct configuration__//
48 -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.
36 +//__Store message merging__//
37 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
49 49  
50 -//__Remove queurying options in Manage__//
51 -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.
39 +//__View all store items__//
40 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
52 52  
42 +//__Out of memory behavior__//
43 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
44 +
45 +//__Max fetch size__//
46 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects the behavior.
47 +
48 +
53 53  == **Fancy Forum Answers** ==
54 54  
55 55  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:
56 56  
57 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
58 58  
59 59  == **Key takeaways** ==
60 60  
... ... @@ -76,5 +76,11 @@
76 76  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  
78 78  ~*~* Indicates a next-generation-architecture only feature.
79 -{{/info}})))((({{toc/}}))){{/container}}
75 +{{/info}}
76 +)))
77 +
78 +(((
79 +{{toc/}}
80 +)))
80 80  {{/container}}
82 +{{/container}}