Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 339.1
edited by Carlijn Kokkeler
on 2024/01/15 14:39
Change comment: There is no comment for this version
To version 120.1
edited by Erik Bakker
on 2023/06/05 15:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +199 - Home Improvements
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,49 +1,59 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release...
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.
7 7  
8 -== **Cloud Template R20 - Double Lane** ==
7 +== **Next generation improvements and bug fixes** ==
9 9  
10 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R20 - Double lane.WebHome||target="blank"]].
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.
11 11  
12 -== **Cloud Template R27 - Single Lane** ==
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 13  
14 -This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
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}}
15 15  
16 -== **Feedback Items** ==
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.
17 17  
18 -//__Failover setup__//
19 -New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
20 +//__Unused images are cleaned up__//
21 +This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan.
20 20  
23 +//__Improved rollup and storage of metrics when running an event streaming solution__//
24 +To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
21 21  
22 -== **Bug Fixes** ==
26 +{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of July. From then on, all data before the 9th of June will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
23 23  
24 -//__Message merging tool__//
25 -The message merging tool has been fixed to allow merging a store item message model into your own message models. In some rare cases your CDM message may be broken due to incorrect data. In those cases, the message mapping and message merge functionalities will be broken as well. If this broken data is detected when navigating to CDM-message-related pages, you will be able to clean your CDM message.
28 +== **Store Improvements** ==
26 26  
27 -//__Catalog topic definitions__//
28 -It is now possible to generate a JSON Example of a topic whose schema has nested elements. Before, an error would occur when trying to generate a JSON example in this case.
30 +//__Improved importing behavior for specific use cases__//
31 +Before, it could happen that a certain placeholder that contained an asterisk (*) were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
29 29  
33 +== **Event Streaming - Certificate Management** ==
34 +
35 +//__Expired certification notification__//
36 +As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
37 +
30 30  == **Fancy Forum Answers** ==
31 31  
32 32  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:
33 33  
34 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
42 +* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
43 +* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
35 35  
36 36  == **Key takeaways** ==
37 37  
38 -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 +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:
39 39  
40 40  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
41 41  * If you have feedback or ideas for us, talk to the Platypus
42 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
51 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
43 43  * Clear your browser cache (Ctrl + Shift + Del)
44 44  * Check out the release notes [here]
45 45  * Start thinking about how the license tracker can aid your development
46 46  * Start thinking about major, minor, and patch
56 +* Upgrade to the latest build number
47 47  * Keep making great integrations
48 48  
49 49  Let's stay in touch and till next time!
... ... @@ -51,11 +51,6 @@
51 51  {{info}}
52 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]]
53 53  
54 -{{/info}}
55 -)))
56 -
57 -(((
58 -{{toc/}}
59 -)))
64 +~*~* Indicates a GEN3-only feature.
65 +{{/info}})))((({{toc/}}))){{/container}}
60 60  {{/container}}
61 -{{/container}}