Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 281.1
edited by CarlijnKokkeler
on 2023/12/04 15:03
Change comment: There is no comment for this version
To version 574.7
edited by dfirdausy
on 2024/07/01 14:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Deployment Delights
1 +224 - Summer Sonata
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.dfirdausy
Content
... ... @@ -3,58 +3,53 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have...
6 +**Hi there, eMagiz developers!** Over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor.
7 7  
8 -== **Alerts** ==
9 -
10 -//__Topic approaching max size alert__//
11 -The alert ‘topic approaching maximum size’ alert 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 -
16 16  == **Feedback Items** ==
9 +//__Retention time and bytes requirements__//
10 +The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes.
17 17  
18 -//__Container version overview__//
19 -In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
14 +//__Used message types__//
15 +It is now possible to filter the message types in Capture on whether they are used.
22 22  
23 -//__Unchanged containers__//
24 -When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
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 ten minutes, this used to be five. Note that the JMS server needs to be updated in order to also store the messages for ten minutes instead of five. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
25 25  
26 -//__Rebuilding of images__//
27 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
28 -
29 -
30 30  == **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.
31 31  
32 -//__Runtime metrics processing__//
33 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
26 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
34 34  
35 -//__Deployment plan__//
36 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
37 37  
38 -//__Store message merging__//
39 -The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
29 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
40 40  
41 -//__View all store items__//
42 -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.
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.
43 43  
44 -//__Out of memory behavior__//
45 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
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.
46 46  
47 -//__Max fetch size__//
48 -We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
49 -
37 +//__View XSLT__//
38 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
50 50  
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.
42 +
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||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"]]
56 56  
57 -== **Key takeaways** ==
52 +== **Key Takeaways** ==
58 58  
59 59  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:
60 60  
... ... @@ -62,10 +62,9 @@
62 62  * If you have feedback or ideas for us, talk to the Platypus
63 63  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64 64  * Clear your browser cache (Ctrl + Shift + Del)
65 -* Check out the release notes [here]
60 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
66 66  * Start thinking about how the license tracker can aid your development
67 67  * Start thinking about major, minor, and patch
68 -* Upgrade to the latest build number
69 69  * Keep making great integrations
70 70  
71 71  Let's stay in touch and till next time!
... ... @@ -73,7 +73,6 @@
73 73  {{info}}
74 74  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75 75  
76 -~*~* Indicates a next-generation-architecture only feature.
77 77  {{/info}}
78 78  )))
79 79