Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 569.1
edited by CarlijnKokkeler
on 2024/06/18 11:55
Change comment: There is no comment for this version
To version 155.1
edited by CarlijnKokkeler
on 2023/10/10 13:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -223 - TBD
1 +206 - Situational Deployment
Content
... ... @@ -1,58 +1,62 @@
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!** 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.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
7 7  
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.
7 +== **Deployment Plan** ==
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
9 +//__Improved deployment plan to make the process better and more predictable__//
10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
13 13  
14 -//__Deprecated warnings__//
15 -We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10.
12 +//__Editing release properties__//
13 +With this release, it will be possible to change the description of a property by editing the property.
16 16  
17 -//__Used message types__//
18 -It is now possible to filter the message types in Capture on whether they are used.
15 +//__JMS memory setting check__//
16 +A change in memory settings triggers redeployment of the container now.
19 19  
20 -[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]]
18 +//__Properties tab__//
19 +We have removed the deprecated tab Properties in the Deploy phase.
21 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.
21 +//__Cleanup old images__//
22 +
23 +== **Store Improvements** ==
24 +
24 24  
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 +== **Feedback Items** ==
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
28 +//__Alerting manual pause__//
29 +A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
30 30  
31 +//__Ordering of graphs in Manage__//
32 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
34 +//__UTC times in Grafana panels__//
35 +All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
33 33  
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.
37 +//__Update flow designer version__//
38 +The framework used in the flow designer has been updated to the latest version.
36 36  
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.
39 39  
40 -//__View XSLT__//
41 -We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
41 +
42 +== **Bug Fixes** ==
42 42  
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.
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.
45 45  
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 +
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 -* [[.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"]]
57 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
54 54  
55 -== **Key Takeaways** ==
59 +== **Key takeaways** ==
56 56  
57 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:
58 58  
... ... @@ -60,9 +60,10 @@
60 60  * If you have feedback or ideas for us, talk to the Platypus
61 61  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
62 62  * Clear your browser cache (Ctrl + Shift + Del)
63 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
67 +* Check out the release notes [here]
64 64  * Start thinking about how the license tracker can aid your development
65 65  * Start thinking about major, minor, and patch
70 +* Upgrade to the latest build number
66 66  * Keep making great integrations
67 67  
68 68  Let's stay in touch and till next time!
... ... @@ -70,11 +70,6 @@
70 70  {{info}}
71 71  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
72 72  
73 -{{/info}}
74 -)))
75 -
76 -(((
77 -{{toc/}}
78 -)))
78 +~*~* Indicates a next-generation-architecture only feature.
79 +{{/info}})))((({{toc/}}))){{/container}}
79 79  {{/container}}
80 -{{/container}}