Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 292.1
edited by Carlijn Kokkeler
on 2023/12/18 12:20
Change comment: There is no comment for this version
To version 115.1
edited by Erik Bakker
on 2023/05/09 13:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +197 - Pay Attention
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,67 +1,63 @@
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!**
5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving our next-generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore, several smaller feedback items and bugs have been resolved with this release. So without further ado, let us dive into all we have to offer.
7 7  
8 -== **TBD** ==
7 +== **Event streaming alerting** ==
9 9  
9 +This release expands our alerting functionality into the event streaming pattern. As of now, one new "static" alert has been introduced for all clients (using event streaming), and two "dynamic" alerts have been introduced that you can configure yourself if there is a need for it.
10 10  
11 +The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights into whether messages on it are deleted due to a size or time constraint. In cases where data is deleted, the topic was too full way before the messages should have been removed due to the retention hours constraint. This alert can indicate that messages might be deleted before consumer groups had the option to consume the messages.
11 11  
12 -== **Feedback Items** ==
13 +The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
13 13  
14 -//__Missing properties overview__//
15 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
15 +[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
16 16  
17 -ADD FIGURE
17 +The first new "dynamic" alert allows you to raise an alert once the number of messages on one (or more topics) is less than a certain number per defined time unit. So, for example, you can configure an alert once the number of messages placed on a topic called "Exception" is less than 15 messages within 5 minutes.
18 18  
19 -//__Container version overview__//
20 -Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
19 +[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
21 +The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups are more than X messages behind on one or more topics. The configuration of this is comparable to what we saw before.
23 23  
24 -//__Improved deployment process__//
25 -The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
23 +For more information on the generic way of working surrounding alerting, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
26 26  
27 -//__Rebuilding of images__//
28 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
25 +== **3rd generation improvements** ==
29 29  
30 -== **Bug Fixes** ==
27 +//__Increased grace period for shutdown__//
28 +In this release, we have increased a container's grace period to shut down before it is forcefully shut down. This should reduce the chance of unwanted failover behavior within your model.
31 31  
32 -//__Runtime metrics processing__//
33 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
30 +//__Update at once or not__//
31 +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.
34 34  
35 -//__Deployment plan__//
36 -We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
33 +//__Improved user feedback while executing a deployment plan__//
34 +This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information about why this cannot be executed is shown to the user. This way, they can take this information and act upon it instead of assuming everything went well.
37 37  
38 -//__View all store items__//
39 -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.
36 +//__Improved auto-healing when running in a hybrid situation__//
37 +In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
40 40  
41 -//__Out of memory behavior__//
42 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
39 +== **Feedback items ** ==
43 43  
44 -//__Max fetch size__//
45 -In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
41 +//__Make sure the message format can be viewed without "Start editing"__//
42 +With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
46 46  
44 +//__Various styling improvements in the flow testing functionality__//
45 +Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
46 +
47 47  == **Fancy Forum Answers** ==
48 48  
49 49  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:
50 50  
51 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
52 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
53 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
54 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
55 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
51 +* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
52 +* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
56 56  
57 -
58 58  == **Key takeaways** ==
59 59  
60 -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:
56 +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:
61 61  
62 62  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63 63  * If you have feedback or ideas for us, talk to the Platypus
64 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
60 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
65 65  * Clear your browser cache (Ctrl + Shift + Del)
66 66  * Check out the release notes [here]
67 67  * Start thinking about how the license tracker can aid your development
... ... @@ -74,12 +74,6 @@
74 74  {{info}}
75 75  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76 76  
77 -~*~* Indicates a next-generation-architecture only feature.
78 -{{/info}}
79 -)))
80 -
81 -(((
82 -{{toc/}}
83 -)))
73 +~*~* Indicates a GEN3-only feature.
74 +{{/info}})))((({{toc/}}))){{/container}}
84 84  {{/container}}
85 -{{/container}}