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 09-MaxVerstappen1 +225 - Pop-up Party - Content
-
... ... @@ -3,69 +3,82 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Wehaveimprovedtheperformanceofourdeploymentplan,it shouldbefinishedmuch quickernow.Nexttothis, we havereleasednew Docker SingleLane andDockerDouble Lane cloud templates. Moreover,severalfeedback itemshavebeenprocessedandsome bugfixes havebeenmade.Lastly,asofthisrelease,the next generationarchitecturewillbeourdefault.6 +**Hi there, eMagiz developers!** In this release, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below! 7 7 8 - {{warning}}9 -P lease be aware that for this release, becauseof the duration of the deployment, we advise you to check your TEST and ACCP cloudslotsstatus, since you mightneedto start them manuallyincaseyourmodel isusing the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.10 - {{/warning}}8 +== **Feedback Items** == 9 +//__Process containers__// 10 +If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern. 11 11 12 -== **Quicker Deployment Plan Execution** == 12 +//__Design settings__// 13 +When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment. 13 13 14 - Wesped up the process of preparing runtime imagesinexecuting the deployment plan. Thestepin the deployment plan concerningthepreparation of runtimeimages will now be executed morequickly and reliably. Moreover, we fixedan issueof the release preparationsteptakinglonger than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.So, the deployment plan will be finished much quicker now!15 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]] 15 15 16 -== **Next Generation Architecture Default** == 17 +//__Untested images__// 18 + 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. 19 + 20 +[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]] 17 17 18 -With this release, the next generation architecture will become the default. New models will use this generation as default. 22 +{{warning}} 23 +The following restrictions apply to this functionality: 19 19 20 -[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]] 25 +* When accepting the risk you accept the risk for the **whole** model. 26 +* If any release based on the same runtime image is already activated on Acceptance you will **not** be warned.{{/warning}} 21 21 22 -== **Cloud Template R11 Docker - Single Lane** == 28 +//__Infinispan Cache Manager__// 29 +We added support for the Infinispan Cache Manager to perform clustering through a new component called GossipRouter. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 30 + 31 +//__Infinispan Cache Manager error message__// 32 +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>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 23 23 24 -This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]]. 34 +//__Flow bump__// 35 +When bumping a new version of all flows using a specific resource, you can specify which version type you want to create, Major, Minor or Patch version. On top of this you can also give more information in a description. 36 + 37 +[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]] 25 25 26 -== **Cloud Template R13 Docker - Double Lane** == 39 +//__Unused support objects__// 40 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'. 27 27 28 -This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]]. 42 +[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]] 43 + 44 +//__Deleting routes__// 45 +For clarity purposes, a confirmation pop-up will be shown when deleting routes. 29 29 30 - == **FeedbackItems** ==47 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]] 31 31 32 -//__Unused properties overview__// 33 -In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are: 49 +//__Debug queue__// 50 +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. 51 + 52 +[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]] 53 + 54 +== **Bug Fixes** == 55 +//__Internal server error__// 56 +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. 34 34 35 -* Not used by any runtime that is in the Create phase release. 36 -* Not required by a flow that is in the Create phase release. 37 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release. 58 +//__Namespace update__// 59 +Editing a namespace used in a message definition automatically updates the message definition & transformations. 38 38 39 -//__ Queue explorermilliseconds__//40 - Thequeuebrowsernowdisplaysmillisecondsin thetimestamps.61 +//__Error pop-up__// 62 +We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows. 41 41 42 -//__ Unusedimages__//43 - When arelease is removed,the relatedunused images in the on-premisesmachines willbe removedaswell.64 +//__SMB inbound channel adapter__// 65 +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>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 44 44 45 -//__ Carwashlogging__//46 - A newloggingfeatureenablingustomakebetter choices inencryption standardswillbe released.67 +//__Heap memory__// 68 +The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 47 47 48 -//__ Staticalertsqueueconsumers__//49 - Alertingwillnowonlygeneratealerts forqueues thatarecreatedandmanagedby theeMagizJMSserver.70 +//__Classpath conflicts__// 71 +We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 50 50 51 -== **Bug Fixes** == 52 - 53 -//__Flow Designer connection line__// 54 -In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas. 55 - 56 -//__Portal for migrated models__// 57 -We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 58 - 59 -//__Error channel inbounds__// 60 -We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow. 61 - 62 62 == **Fancy Forum Answers** == 63 63 64 64 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: 65 65 66 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 77 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 78 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 79 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 67 67 68 -== **Key takeaways** ==81 +== **Key Takeaways** == 69 69 70 70 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: 71 71 ... ... @@ -73,10 +73,9 @@ 73 73 * If you have feedback or ideas for us, talk to the Platypus 74 74 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 75 75 * Clear your browser cache (Ctrl + Shift + Del) 76 -* Check out the release notes [here] 89 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]] 77 77 * Start thinking about how the license tracker can aid your development 78 78 * Start thinking about major, minor, and patch 79 -* Upgrade to the latest build number 80 80 * Keep making great integrations 81 81 82 82 Let's stay in touch and till next time! ... ... @@ -84,7 +84,6 @@ 84 84 {{info}} 85 85 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 86 86 87 -~*~* Indicates a next-generation-architecture only feature. 88 88 {{/info}} 89 89 ))) 90 90