Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
Change comment: There is no comment for this version
To version 281.1
edited by Carlijn Kokkeler
on 2023/12/04 15:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +209 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,53 +1,66 @@
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 worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
6 +**Hi there, eMagiz developers!** We have...
6 6  
7 -== **Next generation improvements and bug fixes** ==
8 +== **Alerts** ==
8 8  
9 -//__Enhanced overview of the HTTP Statistics__//
10 -As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
11 11  
12 -//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13 -In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
14 14  
15 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
16 +== **Feedback Items** ==
16 16  
17 -//__Forced congestion control__//
18 -To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
18 +//__Container version overview__//
19 +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.
19 19  
21 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
20 20  
21 -//__Improved validation errors on the invalid configuration of HTTP outbound components__//
22 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
23 +//__Unchanged containers__//
24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
23 23  
24 -//__Improved migration behavior__//
25 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
26 -A smoother migration of your JMS (and backup JMS) process.
27 -Shortening of names that otherwise would be too long, additional feedback given to the user.
28 -Feedback when the migration process is finished.
26 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
29 29  
30 -//__Additional checks when deploying__//
31 -This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
32 32  
33 -== **Store Improvements** ==
30 +== **Bug Fixes** ==
34 34  
35 -== **Event Streaming - Certificate Management** ==
32 +//__Runtime metrics processing__//
33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
36 36  
35 +//__Deployment plan__//
36 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
37 +
38 +//__Store message merging__//
39 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
40 +
41 +//__View all store items__//
42 +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.
43 +
44 +//__Out of memory behavior__//
45 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
46 +
47 +//__Max fetch size__//
48 +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 its behavior.
49 +
50 +
37 37  == **Fancy Forum Answers** ==
38 38  
39 39  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:
40 40  
41 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
42 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
55 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
43 43  
44 44  == **Key takeaways** ==
45 45  
46 -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:
59 +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:
47 47  
48 48  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
49 49  * If you have feedback or ideas for us, talk to the Platypus
50 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
63 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
51 51  * Clear your browser cache (Ctrl + Shift + Del)
52 52  * Check out the release notes [here]
53 53  * Start thinking about how the license tracker can aid your development
... ... @@ -60,6 +60,12 @@
60 60  {{info}}
61 61  ~* 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 62  
63 -~*~* Indicates a GEN3-only feature.
64 -{{/info}})))((({{toc/}}))){{/container}}
76 +~*~* Indicates a next-generation-architecture only feature.
77 +{{/info}}
78 +)))
79 +
80 +(((
81 +{{toc/}}
82 +)))
65 65  {{/container}}
84 +{{/container}}