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 +206 - Situational Deployment - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,50 +1,64 @@ 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, wefocusedonimproving theusabilityof ourplatformand addressingcommunityfeedback.Specifically, weenhanceduserinterfaceelementson severalpages, includingthedescriptions of help texts, externallinks within helptexts,andtheoveralllayoutofhelp text pages. Additionally, wemade improvementstoseveralpop-up pages. We alsomadetheuserinterfacemore user-friendlyfordebugging integration flows.Lastly,we resolvedan issuefor some modelswhen creatingan Event Processor.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. 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 +== **Deployment Plan** == 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. 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. 14 14 15 -//__ Property valuepage__//16 - Pop-uppageswithnon-editableinput fieldscontaininglong textare now displayingtheentire contentwithoutany textbeingcutoff at theedgeofthepage.21 +//__Cleanup old images__// 22 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 17 17 18 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 24 +== **Store Improvements** == 25 + 19 19 20 -== **Bug Fixes** == 21 -//__Adding tags__// 22 -In the Capture phase, clicking to add or remove a tag in the pop-up page for specifying integration requirements no longer displays a 'blocked' icon. 27 +== **Feedback Items** == 23 23 24 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 29 +//__Alerting manual pause__// 30 +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. 25 25 26 -//__ SMBoutboundgateway__//27 -The SMBoutboundgatewaywiththeGETcommanddidnotwork,thishasbeen resolved.Forthis, anew[[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V310.WebHome||target="blank"]]isavailable.32 +//__Ordering of graphs in Manage__// 33 +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). 28 28 29 -//__T askScheduler__//30 - Inrareoccurences,whenaTaskSchedulerwasused,adeadlocksituation could occurdue tothreadstarvation. Thenumberofthreads availabletothe TaskSchedulerhasbeenincreasedtoresolvethisissue. Forthis,a new[[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V310.WebHome||target="blank"]] isavailable.35 +//__UTC times in Grafana panels__// 36 +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. 31 31 32 -//__ ViewXSLT__//33 - We fixedan issuewiththetransformationtooling, whereit was notpossible toviewan XSLT in certaincases.38 +//__Update flow designer version__// 39 +The framework used in the flow designer has been updated to the latest version. 34 34 35 -//__ Multipart/form-dataHTTPrequest__//36 - TherecommendedSpEL expression used for contructinga multipart/form-data HTTPrequestwas nolonger valid.The[[documentation>>doc:Main.eMagiz Academy.Microlearnings.ExpertLevel.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]]hasbeen updated with thenew standardand the updated expressionis nowpart of our default test suite. The [[legacy documentation>>doc:Main.eMagizAcademy.Microlearnings.LegacyFunctionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] isalso still available.41 +//__Carwash track TLS versions in logging__// 42 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 37 37 44 +//__Moving channels in the flow designer__// 45 +Moving already attached channels in the flow designer has been made sligthly easier. 46 + 47 +//__Topic sizes description change__// 48 +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. 49 + 50 +//__Topic sizes description change__// 51 + 52 +== **Bug Fixes** == 53 + 54 + 38 38 == **Fancy Forum Answers** == 39 39 40 40 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: 41 41 42 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 43 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 44 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 45 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 59 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 46 46 47 -== **Key Takeaways** ==61 +== **Key takeaways** == 48 48 49 49 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 ... ... @@ -52,9 +52,10 @@ 52 52 * If you have feedback or ideas for us, talk to the Platypus 53 53 * 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>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]69 +* Check out the release notes [here] 56 56 * Start thinking about how the license tracker can aid your development 57 57 * Start thinking about major, minor, and patch 72 +* Upgrade to the latest build number 58 58 * Keep making great integrations 59 59 60 60 Let's stay in touch and till next time! ... ... @@ -62,11 +62,6 @@ 62 62 {{info}} 63 63 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 64 64 65 -{{/info}} 66 -))) 67 - 68 -((( 69 -{{toc/}} 70 -))) 80 +~*~* Indicates a next-generation-architecture only feature. 81 +{{/info}})))((({{toc/}}))){{/container}} 71 71 {{/container}} 72 -{{/container}}