Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 480.1
edited by CarlijnKokkeler
on 2024/04/23 13:24
Change comment: There is no comment for this version
To version 113.1
edited by Erik Bakker
on 2023/05/09 12:59
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,74 +1,69 @@
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. 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 work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that 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 +With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is 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 whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication 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 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 -//__Flow test stack trace__//
23 -If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab.
17 +The first new "dynamic" alert allows you to raise an alert once the total 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 message placed on a topic called "Exception" is less than 15 messages within 5 minutes.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
19 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
26 26  
27 -{{info}}TBD{{/info}}
21 +The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
28 28  
29 -== **Bug Fixes** ==
30 -//__Error handling__//
31 -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.
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"]].
32 32  
33 -//__Volume mapping passwords__//
34 -Passwords for network volumes are hidden on the machine after deployment.
25 +== **3rd generation improvements** ==
35 35  
36 -//__Create integration removal__//
37 -When removing an integration from Create, the Create phase is now correctly updated.
27 +//__Increased grace period for shutdown__//
28 +In this release, we have increased the grace period a container gets to shutdown before it is forcefully shutdown. This should reduce the chance of unwanted failover behavior to pop-up within your model.
38 38  
39 -//__Legacy statistics__//
40 -Legacy pages are now correctly hidden when running on the current runtime architecture.
30 +//__Update at once or not__//
31 +This release fixes 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.
41 41  
42 -//__Unused properties__//
43 -Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
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 of 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.
44 44  
45 -//__Enumeration values__//
46 -Enumeration values for event processors can now be edited in Create.
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.
47 47  
48 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
39 +== **Feedback items ** ==
49 49  
50 -//__SFTP sessions__//
51 -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 [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
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.
52 52  
44 +//__Various styling improvements in the flow testing functionality__//
45 +Various smaller styling improvements have been added to the flow testing functionality to improve the overall user experience. For a complete list and more details please check out the release notes.
46 +
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 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
58 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
59 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
51 +* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
52 +* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
53 +* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
60 60  
61 -== **Key Takeaways** ==
55 +== **Key takeaways** ==
62 62  
63 -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:
57 +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:
64 64  
65 65  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
66 66  * If you have feedback or ideas for us, talk to the Platypus
67 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
61 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
68 68  * Clear your browser cache (Ctrl + Shift + Del)
69 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]]
63 +* Check out the release notes [here]
70 70  * Start thinking about how the license tracker can aid your development
71 71  * Start thinking about major, minor, and patch
66 +* Upgrade to the latest build number
72 72  * Keep making great integrations
73 73  
74 74  Let's stay in touch and till next time!
... ... @@ -76,11 +76,6 @@
76 76  {{info}}
77 77  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  
79 -{{/info}}
80 -)))
81 -
82 -(((
83 -{{toc/}}
84 -)))
74 +~*~* Indicates a GEN3-only feature.
75 +{{/info}})))((({{toc/}}))){{/container}}
85 85  {{/container}}
86 -{{/container}}