Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 570.1
edited by CarlijnKokkeler
on 2024/06/18 12:08
Change comment: There is no comment for this version
To version 291.1
edited by CarlijnKokkeler
on 2023/12/06 14:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -223 - Idyllic Image
1 +210 - Deployment Delights
Content
... ... @@ -3,54 +3,62 @@
3 3  (((
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.
6 +**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7 7  
8 +== **Alerts** ==
9 +
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
12 +
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
15 +
8 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.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
18 +//__Improved release build process__//
19 +When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
13 13  
14 -//__Used message types__//
15 -It is now possible to filter the message types in Capture on whether they are used.
21 +//__Container version overview__//
22 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]]
18 -
19 -//__Debugger duration__//
20 -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.
24 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
21 21  
22 -== **Bug Fixes** ==
23 -//__SFTP sessions__//
24 -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 +//__Improved deployment process__//
27 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
29 +//__Rebuilding of images__//
30 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
27 27  
32 +== **Bug Fixes** ==
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
34 +//__Runtime metrics processing__//
35 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
30 30  
31 -//__SMB outbound gateway__//
32 -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 +//__Deployment plan__//
38 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
33 33  
34 -//__TaskScheduler__//
35 -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.
40 +//__View all store items__//
41 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
36 36  
37 -//__View XSLT__//
38 -We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
43 +//__Out of memory behavior__//
44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
39 39  
40 -//__Multipart/form-data HTTP request__//
41 -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.
46 +//__Max fetch size__//
47 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
42 42  
43 43  == **Fancy Forum Answers** ==
44 44  
45 45  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:
46 46  
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"]]
53 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
51 51  
52 -== **Key Takeaways** ==
53 53  
60 +== **Key takeaways** ==
61 +
54 54  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:
55 55  
56 56  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -57,9 +57,10 @@
57 57  * If you have feedback or ideas for us, talk to the Platypus
58 58  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
59 59  * Clear your browser cache (Ctrl + Shift + Del)
60 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
68 +* Check out the release notes [here]
61 61  * Start thinking about how the license tracker can aid your development
62 62  * Start thinking about major, minor, and patch
71 +* Upgrade to the latest build number
63 63  * Keep making great integrations
64 64  
65 65  Let's stay in touch and till next time!
... ... @@ -67,6 +67,7 @@
67 67  {{info}}
68 68  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
69 69  
79 +~*~* Indicates a next-generation-architecture only feature.
70 70  {{/info}}
71 71  )))
72 72