Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 605.1
edited by CarlijnKokkeler
on 2024/07/16 14:41
on 2024/07/16 14:41
Change comment:
There is no comment for this version
To version 150.1
edited by Erik Bakker
on 2023/08/29 10:57
on 2023/08/29 10:57
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 25-Pop-upParty1 +204 - Found It - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,96 +1,49 @@ 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!** Inthisrelease,anew runtime image (LINK) willbeavailable, including changestoour infinispancachemanager,SMBinboundchanneladapter,and heapmemoryconfiguration.Moreover, we have madeprogressonour alertingimprovement plans andhave improvedandadded severalpop-upscreens. Findoutall wereleasedbelow!5 +**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack. 7 7 8 8 == **Feedback Items** == 9 -//__Alerting notification settings__// 10 10 11 -//__ Processcontainers__//12 - Ifamodeldoesnothavea licenseforapattern, the modelcontactnow hastheoption to deletethe processcontainerof thatgivenpattern.9 +//__Improved check on nested property placeholders__// 10 +To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing. 13 13 14 -//__ Designsettings__//15 -Whe npressingApplysettingsinDesignSettings,aconfirmationscreenwillnowbeshown topresent thechangesthatwillbetakeninto effectforeach environment.12 +//__Removed outdated properties when deploying on the new generation architecture stack__// 13 +We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before in order to connect to a Kafka cluster but have become obsolete once you migrate. 16 16 17 - [[image:Main.Images.ReleaseBlog.WebHome@release-225-design-settings.png]]15 +{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}} 18 18 19 -//__Untested images__// 20 - A warning will be shown when a release is activated on **Production** with a new runtime image version which has not been tested on acceptance before. 21 - 22 -[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]] 23 - 24 -{{warn}} 25 -The following restrictions apply to this functionality: 26 - 27 -- The warning is 28 -{{/warn}} 17 +//__Improved performance Manage Dashboards__// 18 +We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture. 29 29 30 -//__Infinispan Cache Manager__// 31 -We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available. 32 - 33 -//__Infinispan Cache Manager error message__// 34 -We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available. 35 - 36 -//__Flow bump__// 37 -When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description. 38 - 39 -[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]] 40 - 41 -//__Unused support objects__// 42 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'. 43 - 44 -[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]] 45 - 46 -//__Deleting routes__// 47 -For clarity purposes, a confirmation pop-up will be shown when deleting routes. 48 - 49 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]] 50 - 51 -//__Debug queue__// 52 -The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it. 53 - 54 -[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]] 55 - 56 56 == **Bug Fixes** == 57 -//__Internal server error__// 58 -The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it. 59 59 60 -//__ Namespaceupdate__//61 - Editinganamespaceusedinamessagedefinitionautomaticallyupdates the messagedefinition&transformations.22 +//__Errors with long stack traces or long message histories will now also show in eMagiz__// 23 +We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s). 62 62 63 -//__ Errorpop-up__//64 -We fixed a nissuewhereapop-upwasshownwithanincorrecterrorwhileediting the message mapping ofasynchronousflows.25 +//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__// 26 +We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration. 65 65 66 -//__SMB inbound channel adapter__// 67 -The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new runtime image LINK is available. 68 - 69 -//__Heap memory__// 70 -The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available. 71 - 72 -//__Classpath conflicts__// 73 -We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. For this, a new runtime image LINK is available. 74 - 75 75 == **Fancy Forum Answers** == 76 76 77 77 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: 78 78 79 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 80 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 81 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 32 +* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]] 33 +* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]] 82 82 83 -== **Key Takeaways** ==35 +== **Key takeaways** == 84 84 85 85 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: 86 86 87 87 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 88 88 * If you have feedback or ideas for us, talk to the Platypus 89 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 41 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 90 90 * Clear your browser cache (Ctrl + Shift + Del) 91 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]43 +* Check out the release notes [here] 92 92 * Start thinking about how the license tracker can aid your development 93 93 * Start thinking about major, minor, and patch 46 +* Upgrade to the latest build number 94 94 * Keep making great integrations 95 95 96 96 Let's stay in touch and till next time! ... ... @@ -98,11 +98,6 @@ 98 98 {{info}} 99 99 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 100 100 101 -{{/info}} 102 -))) 103 - 104 -((( 105 -{{toc/}} 106 -))) 54 +~*~* Indicates a next-generation-architecture only feature. 55 +{{/info}})))((({{toc/}}))){{/container}} 107 107 {{/container}} 108 -{{/container}}