Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 185-Getready1 +224 - Summer Sonata - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. eMagiz1 +XWiki.dfirdausy - Content
-
... ... @@ -1,69 +1,75 @@ 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 havebeen hard at workbolsteringour offeringconcerning the upcoming rollout of our newarchitecturestack.Next to that, we havemadeseveral smallupdatesasthisreleasecontainedacompleterevampoftheManage phase.Pleasetakeamoment toreadthebelowcarefullyandwork withthe newflowdesigneras soonaspossibletofamiliarizeyourselfwith thisone.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 -==**Store additions**== 8 -We have released several Store items that can be used in the Design Store and which include complete data models and transformations. See the list below of the components that have these. 9 - 10 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 3.png]] 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. 11 11 12 - ==**AudittrailUserManagement**==13 - Since the introduction of the API Gateway and Event StreamingpatternsineMagiz,thenotion of users and roleshavebeen added to the platform.IntheUser Managementsection in Deploy you willfindthe overview of the usersand roles configuredin your model. With this release we have also added the history tab to thispageinwhich the platform registers thechangesmade in Users & Roles. Atthemomentwhen the user presses the Apply to environmentbutton,thechanges between theprevioushistoryentry and this action areregisteredinthis section.Thepopupthat is displayedwhen pressing Applytoenvironment has been expandedwiththelistof entriesthatwill beadded to this History section.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. 14 14 15 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]] 15 +//__abc__// 16 +abc. 16 16 17 - ==**Next GenerationMonitoring & Alertingengine**==18 - In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.19 - 20 - *In the Manage phasewe have introduced proper meansto toggle between data of the current and the new monitoringstack (transitionto the new runtime can be a runtime by runtime approach).21 - *Wehave alsoreleasedanddescribedthenewManagephasegraphsin[[Releaseblog183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].22 - * In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)23 - * Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.24 - * The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms25 - 26 - 27 - === **Improvements** ===28 - 29 - *PerformanceDeploymentplan30 - When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.31 - 32 - *FlowDesigner updates33 - We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.34 - 35 - [[image:Main.Images.ReleaseBlog.WebHome@185-Releaseblog2.png]]36 - 37 - * Store38 - Wehavefixedseveral smallerStore importissues to improve the user experience.39 - 18 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 19 + 20 +== **Bug Fixes** == 21 +//__SFTP sessions__// 22 +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. 23 + 24 + 25 + 26 + 27 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 28 + 29 +//__SMB outbound gateway__// 30 +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. 31 + 32 +//__TaskScheduler__// 33 +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. 34 + 35 +//__View XSLT__// 36 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases. 37 + 38 +//__Multipart/form-data HTTP request__// 39 +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. 40 + 40 40 == **Fancy Forum Answers** == 41 41 42 -As always, a gentle reminder to a ll 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:43 +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: 43 43 44 -* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]] 45 -* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]] 45 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 46 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 47 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 48 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 46 46 47 -== **Key takeaways** ==50 +== **Key Takeaways** == 48 48 49 -Thanks to all thathelp build,those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:52 +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: 50 50 51 51 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 52 52 * If you have feedback or ideas for us, talk to the Platypus 53 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 56 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 54 54 * Clear your browser cache (Ctrl + Shift + Del) 55 -* Check out the release notes [here] 58 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]] 56 56 * Start thinking about how the license tracker can aid your development 57 57 * Start thinking about major, minor, and patch 58 -* Upgrade to the latest build number 59 59 * Keep making great integrations 60 -* Check out the new documentation portal. 61 61 62 62 Let's stay in touch and till next time! 63 63 64 64 {{info}} 65 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 66 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 66 66 67 -~*~* Indicates a GEN3-only feature. 68 -{{/info}})))((({{toc/}}))){{/container}} 68 +{{/info}} 69 +))) 70 + 71 +((( 72 +{{toc/}} 73 +))) 69 69 {{/container}} 75 +{{/container}}