Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 159.1
edited by CarlijnKokkeler
on 2023/10/11 09:22
Change comment: There is no comment for this version
To version 574.11
edited by dfirdausy
on 2024/07/01 14:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +224 - Summer Sonata
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.dfirdausy
Content
... ... @@ -1,74 +1,51 @@
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 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.
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.
6 6  
7 -== **Deployment Plan** ==
8 +== **Feedback Items** ==
9 +//__Integration requirements: retention duration and bytes__//
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.
8 8  
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.
11 -
12 -//__Editing release properties__//
13 -With this release, it will be possible to change the description of a property by editing the property.
14 -
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
17 -
18 -//__Properties tab__//
19 -We have removed the deprecated tab Properties in the Deploy phase.
20 -
21 -//__Cleanup old images__//
22 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
23 -
24 -//__Performance improvements for loading releases__//
25 -Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
26 -
27 -== **Store Improvements** ==
12 +//__Integration requirements: Help text__//
13 +Collapsing the help text of this pop-up page by clicking the "?" icon on the top right corner of the pop-up page will now correctly hide the help text pane.
28 28  
15 +//__Debugger duration__//
16 +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.
29 29  
30 -== **Feedback Items** ==
18 +== **Bug Fixes** ==
19 +//__SFTP sessions__//
20 +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 -//__Alerting manual pause__//
33 -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.
22 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
34 34  
35 -//__Ordering of graphs in Manage__//
36 -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).
37 37  
38 -//__UTC times in Grafana panels__//
39 -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.
25 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
40 40  
41 -//__Update flow designer version__//
42 -The framework used in the flow designer has been updated to the latest version.
27 +//__SMB outbound gateway__//
28 +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 -//__Carwash track TLS versions in logging__//
45 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
30 +//__TaskScheduler__//
31 +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 -//__Moving channels in the flow designer__//
48 -Moving already attached channels in the flow designer has been made sligthly easier.
33 +//__View XSLT__//
34 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
49 49  
50 -//__Topic sizes description change__//
51 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
36 +//__Multipart/form-data HTTP request__//
37 +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.
52 52  
53 -//__Password change notification__//
54 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
55 -
56 -//__Password comparison__//
57 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
58 -
59 -
60 -== **Bug Fixes** ==
61 -
62 -//__Flow designer styling__//
63 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
64 -
65 65  == **Fancy Forum Answers** ==
66 66  
67 67  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:
68 68  
69 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
43 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
44 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
45 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
46 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
70 70  
71 -== **Key takeaways** ==
48 +== **Key Takeaways** ==
72 72  
73 73  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:
74 74  
... ... @@ -76,10 +76,9 @@
76 76  * If you have feedback or ideas for us, talk to the Platypus
77 77  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
78 78  * Clear your browser cache (Ctrl + Shift + Del)
79 -* Check out the release notes [here]
56 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
80 80  * Start thinking about how the license tracker can aid your development
81 81  * Start thinking about major, minor, and patch
82 -* Upgrade to the latest build number
83 83  * Keep making great integrations
84 84  
85 85  Let's stay in touch and till next time!
... ... @@ -87,6 +87,11 @@
87 87  {{info}}
88 88  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
89 89  
90 -~*~* Indicates a next-generation-architecture only feature.
91 -{{/info}})))((({{toc/}}))){{/container}}
66 +{{/info}}
67 +)))
68 +
69 +(((
70 +{{toc/}}
71 +)))
92 92  {{/container}}
73 +{{/container}}