Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From 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
To version 569.2
edited by CarlijnKokkeler
on 2024/06/18 11:56
on 2024/06/18 11:56
Change comment:
Update document after refactoring.
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 199-HomeImprovements1 +223 - Idyllic Image - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,57 +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 onimprovingvariousaspectsofourhome.Amongothers we haveimprovedthe logging,alerting, andsecurityof our next-generationarchitecture.Ontopofthat we haveimprovedtheinner workings ofthestore and thecertificate managementforthose ofususingtheEventStreaming pattern.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 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. 12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 11 11 12 -//__ Reason whyruntimecannotstart isnowinthe vast majority of cases reported back__//13 - In this release,wehaveimproved theway wereportfailures during startupofruntimes.This will ensurethatitbecomesmuch easiertopinpointwhat went wrongupon startup.14 +//__Deprecated warnings__// 15 +We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10. 14 14 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}} 17 +//__Used message types__// 18 +It is now possible to filter the message types in Capture on whether they are used. 16 16 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. 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. 19 19 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. 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. 22 22 23 - == **StoreImprovements** ==29 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]] 24 24 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. 27 27 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. 32 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 30 30 31 -== **Event Streaming - Certificate Management** == 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. 32 32 33 -//__ Expiredcertification notification__//34 - As ofnowwe havefunctionalityinplacethat will informyou (andus) whenaclientcertificateof anEventStreaminguseris goingtoexpirewithinthe upcoming threemonths.This way you can take action early onand reportbackthattheupdate wassuccesfullsowe canrevoke the expiringclientcertificate accordingly.If you wantspecificinformationonthis pleasereachoutto usat [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].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. 35 35 40 +//__View XSLT__// 41 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases. 42 + 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. 45 + 36 36 == **Fancy Forum Answers** == 37 37 38 38 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: 39 39 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"]] 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"]] 42 42 43 -== **Key takeaways** ==55 +== **Key Takeaways** == 44 44 45 -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: 46 46 47 47 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 48 48 * If you have feedback or ideas for us, talk to the Platypus 49 -* 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. 50 50 * Clear your browser cache (Ctrl + Shift + Del) 51 -* Check out the release notes [here] 63 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] 52 52 * Start thinking about how the license tracker can aid your development 53 53 * Start thinking about major, minor, and patch 54 -* Upgrade to the latest build number 55 55 * Keep making great integrations 56 56 57 57 Let's stay in touch and till next time! ... ... @@ -59,6 +59,11 @@ 59 59 {{info}} 60 60 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 62 -~*~* Indicates a GEN3-only feature. 63 -{{/info}})))((({{toc/}}))){{/container}} 73 +{{/info}} 74 +))) 75 + 76 +((( 77 +{{toc/}} 78 +))) 64 64 {{/container}} 80 +{{/container}}