Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 574.11
edited by dfirdausy
on 2024/07/01 14:33
on 2024/07/01 14:33
Change comment:
There is no comment for this version
To version 123.1
edited by Erik Bakker
on 2023/06/08 08:11
on 2023/06/08 08:11
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 224-SummerSonata1 +199 - Home Improvements - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,61 +1,57 @@ 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!** Overthepast week, wefocused on improvingtheusabilityof ourplatformand addressingcommunity feedback.Specifically,weenhanceduserinterfaceelementsonseveralpages,includingthedescriptionsofhelptexts,external links within helptexts,andtheoveralllayout ofhelptext pages. Additionally,wemade improvementstoseveralpop-up pages.We alsomadetheuser interface moreuser-friendlyfor debuggingintegrationflows. Lastly, weresolved anissueforsomemodelswhencreating an EventProcessor.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern. 7 7 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. 7 +== **Next generation improvements and bug fixes** == 11 11 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 - 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. 9 +//__Enhanced overview of the HTTP Statistics__// 10 +As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort. 17 17 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. 12 +//__Reason why runtime cannot start is now in the vast majority of cases reported back__// 13 +In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup. 21 21 22 - [[image:Main.Images.ReleaseBlog.WebHome@release-223-known-hosts.png]]15 +{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 23 23 17 +//__Forced congestion control__// 18 +To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 20 +//__Unused images are cleaned up__// 21 +This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan. 26 26 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. 23 +== **Store Improvements** == 29 29 30 -//__ TaskScheduler__//31 - In rareoccurences,whena TaskSchedulerwas used,adeadlocksituation couldoccurdueto threadstarvation. The numberofthreadsavailabletotheTaskSchedulerhas been increased toresolve this issue.Forthis,anew[[runtime image>>doc:Main.ReleaseInformation.RuntimeImages.V310.WebHome||target="blank"]]isavailable.25 +//__Improved importing behavior for specific use cases__// 26 +Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users. 32 32 33 -//__ ViewXSLT__//34 - Wefixedanissuewiththetransformation tooling,whereit wasnotpossibletoviewan XSLT in certain cases.28 +//__Fixed bug in creating a message mapping on top of an imported system message__// 29 +It is now possbile to create a message mapping to an imported system message from the store. 35 35 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. 31 +== **Event Streaming - Certificate Management** == 38 38 33 +//__Expired certification notification__// 34 +As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 35 + 39 39 == **Fancy Forum Answers** == 40 40 41 41 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: 42 42 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"]] 40 +* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]] 41 +* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]] 47 47 48 -== **Key Takeaways** ==43 +== **Key takeaways** == 49 49 50 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:45 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 51 51 52 52 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 53 53 * If you have feedback or ideas for us, talk to the Platypus 54 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 49 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 55 55 * Clear your browser cache (Ctrl + Shift + Del) 56 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]51 +* Check out the release notes [here] 57 57 * Start thinking about how the license tracker can aid your development 58 58 * Start thinking about major, minor, and patch 54 +* Upgrade to the latest build number 59 59 * Keep making great integrations 60 60 61 61 Let's stay in touch and till next time! ... ... @@ -63,11 +63,6 @@ 63 63 {{info}} 64 64 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 65 65 66 -{{/info}} 67 -))) 68 - 69 -((( 70 -{{toc/}} 71 -))) 62 +~*~* Indicates a GEN3-only feature. 63 +{{/info}})))((({{toc/}}))){{/container}} 72 72 {{/container}} 73 -{{/container}}