Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 124.1
edited by Erik Bakker
on 2023/06/19 14:21
on 2023/06/19 14:21
Change comment:
There is no comment for this version
To version 569.1
edited by CarlijnKokkeler
on 2024/06/18 11:55
on 2024/06/18 11:55
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 -2 00-UnchartedTerritories1 +223 - TBD - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,66 +1,68 @@ 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!** In the lastfewweeks, we have worked hard onalot ofthingsthat areunfortanetlynot quite readytobe released.Asaresultthe ouputofthis release islimited.Havingsaid thatwestillbringsomekey improvementsintheDeployandManagephasethatwouldmakelifemucheasier.6 +**Hi there, eMagiz developers!** In the past week, we have worked hard to release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]]. This image contains several bug fixes, and increases the debugger duration. Next to this, improvements have been done to the SwaggerUI settings, we have resolved more deprecated warnings to prepare for Mendix version 10, and it is now possible to filter on the use of message types in Capture. Moreover, we have done bug fixes related to viewing an XSLT and SpEL expressions used for contructing a multipart/form-data HTTP request. 6 6 7 -== **Next generation improvements and bug fixes** == 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. 8 8 9 -//__Enhanced right-hand view within Deployment Plan context__// 10 -When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview. 12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 11 11 12 -{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}} 14 +//__Deprecated warnings__// 15 +We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10. 13 13 14 -//__ Improvedtimeoutsettingswhendeploying__//15 - Toavoid mismatchesbetweenvariousparts ofthe infrastructurewe have improvedthetimeout configuration on certaindeploymentplanstepstoreducethechancethatthesemismatchesoccur.17 +//__Used message types__// 18 +It is now possible to filter the message types in Capture on whether they are used. 16 16 17 -{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 20 +[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]] 21 + 22 +//__Debugger duration__// 23 +Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be reset (or updated) in order to also store the messages for 10 minutes instead of 5. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. 18 18 19 -//__Detailed HTTP Statistics now show user info in specific additional cases__// 20 -To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations. 25 +== **Bug Fixes** == 26 +//__SFTP sessions__// 27 +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. 21 21 22 - {{info}}Note that this fix is part of a new runtime imagefor the next-generationruntimes.Thereleasenotes of this canbe found [[here>>doc:Main.ReleaseInformation.Runtime Images.WebHome||target="blank"]]{{/info}}29 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]] 23 23 24 -//__Improved loading speed of Manage Dashboard__// 25 -This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase. 26 26 27 - == **StoreImprovements** ==32 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 28 28 29 -//__ Importingin Design is improved__//30 - Wehavesolveda bugthat couldcause issueswhen importingsomethinginDesignwhile the accompanyingintegrationwasnotyet inCreate.34 +//__SMB outbound gateway__// 35 +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 31 32 -== **Bug Fixes** == 37 +//__TaskScheduler__// 38 +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. 33 33 34 -//__ Deprecated reminderpop-up removed__//35 -We haveremoved areminderpop-upona pendingcloud templateasit wasdeprecated and couldcause issueswhenusingitin communicationwith othersystems.40 +//__View XSLT__// 41 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases. 36 36 37 -//__ Improved selectionareainFlow Designer__//38 - Whenworkingon a largeflowyoucannowselect specificareas easilywhileyouare scrolled downfurhterdowntheflow.43 +//__Multipart/form-data HTTP request__// 44 +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. 39 39 40 -//__Improved Kafka settings_// 41 -For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them. 42 - 43 -{{info}}We stronly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}} 44 - 45 45 == **Fancy Forum Answers** == 46 46 47 47 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: 48 48 49 -* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]] 50 -* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]] 50 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 51 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 52 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 53 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 51 51 52 -== **Key takeaways** ==55 +== **Key Takeaways** == 53 53 54 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:57 +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 56 56 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 57 57 * If you have feedback or ideas for us, talk to the Platypus 58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 61 +* 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] 63 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] 61 61 * Start thinking about how the license tracker can aid your development 62 62 * Start thinking about major, minor, and patch 63 -* Upgrade to the latest build number 64 64 * Keep making great integrations 65 65 66 66 Let's stay in touch and till next time! ... ... @@ -68,6 +68,11 @@ 68 68 {{info}} 69 69 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 70 70 71 -~*~* Indicates a GEN3-only feature. 72 -{{/info}})))((({{toc/}}))){{/container}} 73 +{{/info}} 74 +))) 75 + 76 +((( 77 +{{toc/}} 78 +))) 73 73 {{/container}} 80 +{{/container}}