Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 152.1
edited by Erik Bakker
on 2023/09/15 08:37
on 2023/09/15 08:37
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 -2 05-WorldExplorers1 +223 - Idyllic Image - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,53 +1,58 @@ 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!** Wehave processedadditionalfeedbackon theManage phasetoensureyou canmoreeasily createoverviewsof yourstatistics,displayingallinformationcorrectlyandimprovingthemigrationprocess to thenext-generationarchitectureintheCreatephaseslightly.On topofthat, we haveimprovedthescalabilityofournewgenerationmonitoringstackandthe alertingstructure.We will alsorelease a newcloudtemplateforour next-generationinfrastructuretocomply with technicalrequirementsfrom ourcloudprovider.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 -== ** Mandatory Cloud Template Upgrade - Next-generation models ** == 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 - As can be seen on our[[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], wewill releasea new cloud templateforour next-generation models(both singleanddoublelane) that will change a configuration in these templatesto complywith technical and operational requirements from our cloud provider.The announcement of the statuspage itself holds more detail for those to whom it pertains.12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 10 10 11 -== **Feedback Items** == 14 +//__Deprecated warnings__// 15 +We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10. 12 12 13 -//__ ImprovedValidation whenmigratingto thenext-generation architecture__//14 - To improvethemigration processto thenext-generationarchitecture,wenowshow a list ofall reportedproblems,allowingtheusertoresolvethem beforemigrating to thenext-generation architecture.17 +//__Used message types__// 18 +It is now possible to filter the message types in Capture on whether they are used. 15 15 16 -{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/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. 17 17 18 -//__Improved HTTP Statistics__// 19 -To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview. 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. 20 20 21 -//__Show values on the runtime level in Deploy Architecture__// 22 -We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution. 29 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]] 23 23 24 -{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence. 25 -* JMS - The number of queues in the active release. 26 -* Messaging Container - The number of messaging integrations in the active release. 27 -* Messaging Connector - The number of messaging integrations related to this system in the active release. 28 -* API Gateway Container - The number of operations in the active release. 29 -* Event Streaming Container - The number of event processors in the active release. 30 30 31 - There might bemulti-tenant and multi-runtimesituations that do not always get totheexact number; however, thisisagreatimprovement compared to showingno values.{{/info}}32 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 32 32 33 -== **Bug Fixes** == 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. 34 34 35 -//__ Gain the ability again to configure certificatesin Deploy Architectureagain__//36 -In r estricting theconfigurationoptionson thecertificatelevel in one of ourlatterreleases,itbecame impossiblefornormalusersto addandeditcertificateswithin DeployArchitecture.To resolvethisproblem wehavenowreleaseda fixto resolve this issue,giving peoplethe abilityagain toaddandedit certificatesunderDeployArchitecture.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. 37 37 38 -//__ Ensure that differingcontainer configurations deploy the correct configuration__//39 -W henyou runinamulti-runtimeconfiguration and changetheactual flows that need torun on container A vs. container B, it happened before thatall flowswere still beingdeployed on allruntimes.Withthis release,we will feed this informationcorrectly to our infrastructure to ensure the correctand configured flowsaredeployedontheproper containers.40 +//__View XSLT__// 41 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases. 40 40 41 -//__ Remove queurying options in Manage__//42 -T oavoid errorsandloading problems whenanalyzingyour statisticsin Manage,wehaveremovedthe optiontoselect adefaulttimerange spanning morethansevendays.This is toguaranteethestabilityof thesolutionandtoavoidusers getting unnecessaryerrors.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. 43 43 44 44 == **Fancy Forum Answers** == 45 45 46 46 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: 47 47 48 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||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"]] 49 49 50 -== **Key takeaways** ==55 +== **Key Takeaways** == 51 51 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 ... ... @@ -55,10 +55,9 @@ 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] 63 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] 59 59 * Start thinking about how the license tracker can aid your development 60 60 * Start thinking about major, minor, and patch 61 -* Upgrade to the latest build number 62 62 * Keep making great integrations 63 63 64 64 Let's stay in touch and till next time! ... ... @@ -66,6 +66,11 @@ 66 66 {{info}} 67 67 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 68 68 69 -~*~* Indicates a next-generation-architecture only feature. 70 -{{/info}})))((({{toc/}}))){{/container}} 73 +{{/info}} 74 +))) 75 + 76 +((( 77 +{{toc/}} 78 +))) 71 71 {{/container}} 80 +{{/container}}