Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 473.1
edited by CarlijnKokkeler
on 2024/04/23 12:21
Change comment: There is no comment for this version
To version 114.1
edited by Erik Bakker
on 2023/05/09 13:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -219 - Creation Carousel
1 +197 - Pay Attention
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,67 +1,68 @@
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, we introduce new environment templates for Docker single and double lane. The Moreover, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
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 -== **Environment Template R13 Docker - Single Lane** ==
9 -This release introduces a new non-service affecting environment template for all our customers running in a single-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Single Lane.WebHome||target="blank"]].
7 +== **Event streaming alerting** ==
10 10  
11 -== **Environment Template R15 Docker - Double Lane** ==
12 -This release introduces a new non-service affecting environment template for all our customers running in a double-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R15 Docker - Double Lane.WebHome||target="blank"]].
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.
13 13  
14 -== **Feedback Items** ==
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.
15 15  
16 -//__eMagiz Mendix connector__//
17 -We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
13 +The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
18 18  
19 -//__Improved OpenAPI import__//
20 -The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
15 +[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
21 21  
22 -== **Bug Fixes** ==
23 -//__Error handling__//
24 -When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
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.
25 25  
26 -//__Volume mapping passwords__//
27 -Passwords for network volumes are hidden on the machine after deployment.
19 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
28 28  
29 -//__Create integration removal__//
30 -When removing an integration from Create, the Create phase is correctly updated as well.
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.
31 31  
32 -//__Legacy statistics__//
33 -Legacy pages are now correctly hidden when running on the current runtime architecture.
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"]].
34 34  
35 -//__Unused properties__//
36 -Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
25 +== **3rd generation improvements** ==
37 37  
38 -//__Enumeration values__//
39 -Enumeration values for event processors can now be edited in Create.
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.
40 40  
41 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
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.
42 42  
43 -//__SFTP sessions__//
44 -SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
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.
45 45  
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.
38 +
39 +== **Feedback items ** ==
40 +
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.
43 +
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 +
46 46  == **Fancy Forum Answers** ==
47 47  
48 48  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:
49 49  
50 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
51 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
52 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||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"]]
53 53  
54 -== **Key Takeaways** ==
54 +== **Key takeaways** ==
55 55  
56 -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:
57 57  
58 58  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
59 59  * If you have feedback or ideas for us, talk to the Platypus
60 -* 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.
61 61  * Clear your browser cache (Ctrl + Shift + Del)
62 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
62 +* Check out the release notes [here]
63 63  * Start thinking about how the license tracker can aid your development
64 64  * Start thinking about major, minor, and patch
65 +* Upgrade to the latest build number
65 65  * Keep making great integrations
66 66  
67 67  Let's stay in touch and till next time!
... ... @@ -69,11 +69,6 @@
69 69  {{info}}
70 70  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71 71  
72 -{{/info}}
73 -)))
74 -
75 -(((
76 -{{toc/}}
77 -)))
73 +~*~* Indicates a GEN3-only feature.
74 +{{/info}})))((({{toc/}}))){{/container}}
78 78  {{/container}}
79 -{{/container}}