Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 151.1
edited by Erik Bakker
on 2023/09/13 07:02
Change comment: There is no comment for this version
To version 561.1
edited by CarlijnKokkeler
on 2024/06/18 11:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +223 - TBD
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,62 +1,55 @@
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!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
6 -
7 -== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
8 -
9 -As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
10 -
6 +**Hi there, eMagiz developers!**
7 +
11 11  == **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.
12 12  
13 -//__Improved Validation when migrating to the next-generation architecture__//
14 -To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
15 15  
16 -{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
14 +//__Deprecated warnings__//
15 +We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10.
17 17  
18 -//__Improved HTTP Statistics__//
19 -To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
17 +//__Used message types__//
18 +It is now possible to filter the message types in Capture on whether they are used.
20 20  
21 -//__"Topic Full" alert restriction changed__//
22 -With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better.
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.
23 23  
24 -//__Improved performance Manage Dashboards__//
25 -We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
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.
26 26  
27 -//__Show values on the runtime level in Deploy Architecture__//
28 -We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
29 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
29 29  
30 -{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
31 -* JMS - The number of queues in the active release.
32 -* Messaging Container - The number of messaging integrations in the active release.
33 -* Messaging Connector - The number of messaging integrations related to this system in the active release.
34 -* API Gateway Container - The number of operations in the active release.
35 -* Event Streaming Container - The number of event processors in the active release.
36 36  
37 -There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
32 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
38 38  
39 -== **Bug Fixes** ==
34 +//__SFTP sessions__//
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.
40 40  
41 -//__Improved information Queue Statistics__//
42 -Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release.
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.
43 43  
44 -//__Gain the ability again to configure certificates in Deploy Architecture again__//
45 -In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
40 +//__View XSLT__//
41 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
46 46  
47 -//__Ensure that differing container configurations deploy the correct configuration__//
48 -When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
49 -
50 -//__Remove queurying options in Manage__//
51 -To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
52 -
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 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
47 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
48 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
49 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
50 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
58 58  
59 -== **Key takeaways** ==
52 +== **Key Takeaways** ==
60 60  
61 61  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  
... ... @@ -64,10 +64,9 @@
64 64  * If you have feedback or ideas for us, talk to the Platypus
65 65  * 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]
60 +* 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 next-generation-architecture only feature.
79 -{{/info}})))((({{toc/}}))){{/container}}
70 +{{/info}}
71 +)))
72 +
73 +(((
74 +{{toc/}}
75 +)))
80 80  {{/container}}
77 +{{/container}}