Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 116.1
edited by Erik Bakker
on 2023/05/10 08:46
Change comment: There is no comment for this version
To version 568.1
edited by CarlijnKokkeler
on 2024/06/18 11:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +223 - Idyllic Image
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,73 +1,68 @@
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 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.
6 +**Hi there, eMagiz developers!** In the past week, we have worked hard to release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]]. This image contains several bug fixes, and increases the debugger duration. Next to this, improvements have been done to the SwaggerUI settings, we have resolved more deprecated warnings to prepare for Mendix version 10, and it is now possible to filter on the use of message types in Capture. Moreover, we have done bug fixes related to viewing an XSLT and SpEL expressions used for contructing a multipart/form-data HTTP request.
6 6  
7 -== **Event streaming alerting** ==
8 +== **Feedback Items** ==
9 +//__SwaggerUI default__//
10 +Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown.
8 8  
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.
12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
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.
14 +//__Deprecated warnings__//
15 +We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10.
12 12  
13 -The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
17 +//__Used message types__//
18 +It is now possible to filter the message types in Capture on whether they are used.
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
20 +[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]]
21 +
22 +//__Debugger duration__//
23 +Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be reset (or updated) in order to also store the messages for 10 minutes instead of 5. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
16 16  
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 +== **Bug Fixes** ==
26 +//__SFTP sessions__//
27 +Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
29 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
20 20  
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.
22 22  
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 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
24 24  
25 -== **3rd generation improvements** ==
34 +//__SMB outbound gateway__//
35 +The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
26 26  
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.
37 +//__TaskScheduler__//
38 +In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
29 29  
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.
40 +//__View XSLT__//
41 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
32 32  
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.
43 +//__Multipart/form-data HTTP request__//
44 +The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available.
35 35  
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 -//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
40 -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.
41 -
42 -{{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 June. From then on, all data before the 12th of May 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}}
43 -
44 -== **Feedback items ** ==
45 -
46 -//__Make sure the message format can be viewed without "Start editing"__//
47 -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.
48 -
49 -//__Various styling improvements in the flow testing functionality__//
50 -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.
51 -
52 52  == **Fancy Forum Answers** ==
53 53  
54 54  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:
55 55  
56 -* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
57 -* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
50 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
51 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
52 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
53 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
58 58  
59 -== **Key takeaways** ==
55 +== **Key Takeaways** ==
60 60  
61 -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 +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:
62 62  
63 63  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64 64  * If you have feedback or ideas for us, talk to the Platypus
65 -* 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.
66 66  * Clear your browser cache (Ctrl + Shift + Del)
67 -* Check out the release notes [here]
63 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
68 68  * Start thinking about how the license tracker can aid your development
69 69  * Start thinking about major, minor, and patch
70 -* Upgrade to the latest build number
71 71  * Keep making great integrations
72 72  
73 73  Let's stay in touch and till next time!
... ... @@ -75,6 +75,11 @@
75 75  {{info}}
76 76  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  
78 -~*~* Indicates a GEN3-only feature.
79 -{{/info}})))((({{toc/}}))){{/container}}
73 +{{/info}}
74 +)))
75 +
76 +(((
77 +{{toc/}}
78 +)))
80 80  {{/container}}
80 +{{/container}}