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 -2 24-Summer Sonata1 +210 - Deployment Delights - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -3,52 +3,59 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Overthe pastweek, wefocusedonimproving theusabilityof ourplatformandaddressingcommunity feedback.Specifically, weenhanceduserinterfaceelementsonseveralpages,includingthedescriptionsofhelptexts,externallinks within helptexts,andtheoveralllayoutofhelp text pages.Additionally,we made improvementsto severalpop-uppages. We alsomadetheuser interface moreuser-friendly for debugging integration flows. Lastly, weresolvedanissueforsomemodelswhen creatinganEventProcessor.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 -//__Retention duration 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. 11 11 12 -//__ Usedmessagetypes__//13 -It is now possible to filter themessagetypesinCapture onwhethertheyareused.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. 14 14 15 -[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]] 16 - 17 -//__Debugger duration__// 18 -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. 21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 19 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 +//__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. 23 23 24 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]] 26 +//__Rebuilding of images__// 27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 25 25 29 +== **Bug Fixes** == 26 26 27 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 31 +//__Runtime metrics processing__// 32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 28 28 29 -//__ SMBoutboundgateway__//30 - TheSMBoutboundgatewaywiththeGETcommanddidnotwork,thishas beenresolved.Forthis, a new[[runtimeimage>>doc:Main.Release Information.RuntimeImages.V310.WebHome||target="blank"]]isavailable.34 +//__Deployment plan__// 35 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck. 31 31 32 -//__ TaskScheduler__//33 - Inrare occurences,whenaTaskScheduler wasused, a deadlocksituationcould occurdue tothreadstarvation. The numberofthreadsavailabletothe TaskSchedulerhasbeenincreasedto resolvethisissue.For this, a new[[runtimeimage>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.37 +//__View all store items__// 38 +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. 34 34 35 -//__ ViewXSLT__//36 -We fixedan issue withthe transformationtooling,whereit wasnotpossibletoview anXSLTincertaincases.40 +//__Out of memory behavior__// 41 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 37 37 38 -//__M ultipart/form-dataHTTP request__//39 - TherecommendedSpELexpressionused forcontructinga multipart/form-dataHTTPrequestwas nolongervalid. The[[documentation>>doc:Main.eMagizAcademy.Microlearnings.ExpertLevel.DataHandling.expert-data-handling-multipart-form-data.WebHome||target="blank"]]has beenupdated withthenew standardandthe updatedexpressionisnow part ofour defaulttestsuite.The[[legacydocumentation>>doc:Main.eMagizAcademy.Microlearnings.LegacyFunctionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available.43 +//__Max fetch size__// 44 +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. 40 40 41 41 == **Fancy Forum Answers** == 42 42 43 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: 44 44 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"]] 50 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 51 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 52 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 53 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 54 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 49 49 50 -== **Key Takeaways** == 51 51 57 +== **Key takeaways** == 58 + 52 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: 53 53 54 54 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -55,9 +55,10 @@ 55 55 * If you have feedback or ideas for us, talk to the Platypus 56 56 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 57 57 * Clear your browser cache (Ctrl + Shift + Del) 58 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]65 +* Check out the release notes [here] 59 59 * Start thinking about how the license tracker can aid your development 60 60 * Start thinking about major, minor, and patch 68 +* Upgrade to the latest build number 61 61 * Keep making great integrations 62 62 63 63 Let's stay in touch and till next time! ... ... @@ -65,6 +65,7 @@ 65 65 {{info}} 66 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]] 67 67 76 +~*~* Indicates a next-generation-architecture only feature. 68 68 {{/info}} 69 69 ))) 70 70