Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 23-IdyllicImage1 +206 - Situational Deployment - Content
-
... ... @@ -1,55 +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!** In the past week, we have workedhardtoreleaseanew[[runtime image>>doc:Main.ReleaseInformation.RuntimeImages.V310.WebHome||target="blank"]]. This imagecontainsseveralbug fixes, and increasesthe debugger duration. Next to this,improvementshavebeen done to the SwaggerUIsettings, we haveresolvedmore deprecated warningsto preparefor Mendix version 10, and itisnowpossibletofilteronthe useof messagetypesin Capture.Moreover,wehave done bug fixesrelated to viewingan XSLT and SpEL expressions usedforcontructing a multipart/form-data HTTP request.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 -//__SwaggerUI default__// 10 -Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown. 7 +== **Deployment Plan** == 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 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. 13 13 14 -//__ Usedmessagetypes__//15 - It isnow possible tofilterthemessage typesinCaptureonwhethertheyareused.12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 16 16 17 -[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]] 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. 18 18 19 -//__ Debuggerduration__//20 -W iretapsanddebugging sessions will now collect messagesfor 10 minutes,thisused tobe five.Note that theJMS server needs to be reset (or updated)inorder to also storethemessagesfor ten minutesinsteadof five. Forthis, a new[[runtime image>>doc:Main.ReleaseInformation.RuntimeImages.V310.WebHome||target="blank"]] is available.21 +//__Cleanup old images__// 22 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 21 21 22 -== **Bug Fixes** == 23 -//__SFTP sessions__// 24 -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. 24 +== **Store Improvements** == 25 + 25 25 26 - [[image:Main.Images.ReleaseBlog.WebHome@release-223-known-hosts.png]]27 +== **Feedback Items** == 27 27 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. 28 28 29 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 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). 30 30 31 -//__ SMBoutboundgateway__//32 - TheSMBoutboundgatewaywiththeGET commanddidnotwork,thishasbeenresolved.For this,anew [[runtimeimage>>doc:Main.Release Information.RuntimeImages.V310.WebHome||target="blank"]]is available.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. 33 33 34 -//__ TaskScheduler__//35 - Inrareoccurences, when a TaskSchedulerwasused,a deadlock situationcould occur dueto threadstarvation. The number ofthreads available totheTaskScheduler has beenincreased toresolvethis issue.For this,anew [[runtimeimage>>doc:Main.Release Information.RuntimeImages.V310.WebHome||target="blank"]] isavailable.38 +//__Update flow designer version__// 39 +The framework used in the flow designer has been updated to the latest version. 36 36 37 -//__ ViewXSLT__//38 - Wefixedanissue withthetransformationtooling,whereitwasnotpossibleto viewanXSLTincertaincases.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. 39 39 40 -//__M ultipart/form-dataHTTP request__//41 - The recommended SpEL expressionused for contructing amultipart/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"]] hasbeenupdated withthenewstandard and theupdated expressionis now partof our default testsuite. The[[legacy documentation>>doc:Main.eMagizAcademy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] isalso still available.44 +//__Moving channels in the flow designer__// 45 +Moving already attached channels in the flow designer has been made sligthly easier. 42 42 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 + 43 43 == **Fancy Forum Answers** == 44 44 45 45 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: 46 46 47 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 48 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 49 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 50 -* [[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"]] 51 51 52 -== **Key Takeaways** ==61 +== **Key takeaways** == 53 53 54 54 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: 55 55 ... ... @@ -57,9 +57,10 @@ 57 57 * If you have feedback or ideas for us, talk to the Platypus 58 58 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 59 59 * Clear your browser cache (Ctrl + Shift + Del) 60 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]69 +* Check out the release notes [here] 61 61 * Start thinking about how the license tracker can aid your development 62 62 * Start thinking about major, minor, and patch 72 +* Upgrade to the latest build number 63 63 * Keep making great integrations 64 64 65 65 Let's stay in touch and till next time! ... ... @@ -67,11 +67,6 @@ 67 67 {{info}} 68 68 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 69 69 70 -{{/info}} 71 -))) 72 - 73 -((( 74 -{{toc/}} 75 -))) 80 +~*~* Indicates a next-generation-architecture only feature. 81 +{{/info}})))((({{toc/}}))){{/container}} 76 76 {{/container}} 77 -{{/container}}