Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 90.1
edited by Erik Bakker
on 2023/03/14 06:51
on 2023/03/14 06:51
Change comment:
There is no comment for this version
To version 603.1
edited by Erik Bakker
on 2024/07/16 14:38
on 2024/07/16 14:38
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 194-BigLeap1 +225 - Pop-up Party - Content
-
... ... @@ -1,80 +1,90 @@ 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 th e lastcoupleof weeks,we haveworkedaroundtheclocktoreleasevariousimprovements pointswithin the3rdgenerationruntimeandelsewhere.Amongotherswehaveimprovedthefeedbackprovidedwhenaflow can't startdue to an incorrect transformation.Improvedwhencertain logging is triggerdandimproved thestabilityofourinternalinfrastructure. Ontopofthat wefixed severalbugfixessurroundingotherparts of the platform.Sowithoutfurther adolet us take a look at all theseimprovements.6 +**Hi there, eMagiz developers!** In this release, a new runtime image (LINK) 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! 6 6 7 -== **3rd generation improvements** == 8 +== **Feedback Items** == 9 +//__Alerting notification settings__// 8 8 9 -//__ Betterfeedback in error log when acorrupt stylesheet isencountered__//10 - Wehaveimprovedtheloggingwithin a 3rdgenerationruntimethatidentifiesthebrokenresourcebynamewithinacontainerand informsyouto navigatetoCreate -> Resourcestoseein which flowsthe resourceisusedso youcantake theappropriate action.11 +//__Process containers__// 12 +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 -//__ Betterinternal error handlingto avoid unnecessaryalerting and notifications__//13 -W ehaveimproved theinternal error handlingwhensendingmetricsfromthe runtime to ourmonitoringstack.Thiswillgravelyreduce the numberofalertsyouwillreceiveonthistopicwhenyourmodel runs on the3rd generationmonitoring stack.14 +//__Design settings__// 15 +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. 14 14 15 -//__Improved Manage Dashboard__// 16 -This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture. 17 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]] 17 17 18 -//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__// 19 -When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes. 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]] 20 20 21 -//__Improved process of deploy preparation__// 22 -With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced. 24 +//__Infinispan Cache Manager__// 25 +We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available. 26 + 27 +//__Infinispan Cache Manager error message__// 28 +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. 23 23 24 -//__Improved migration of Streaming container__// 25 -When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention. 30 +//__Flow bump__// 31 +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. 32 + 33 +[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]] 26 26 27 -//__ AddHistorytoNotificationsin Manage__//28 - To improvetheauditabilityof our platform wehave introducedanaudittrail tothe NotificationsectioninManage formodelsrunningon our3rd generationmonitoring stack. This way it is always visiblewhen the notificationswere paused andwho pausedorunpausedthenotifications.35 +//__Unused support objects__// 36 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'. 29 29 30 -//__Improved Manage phase for Event Streaming__// 31 -Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you. 38 +[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]] 39 + 40 +//__Deleting routes__// 41 +For clarity purposes, a confirmation pop-up will be shown when deleting routes. 32 32 33 -//__Improved help text for network volumes__// 34 -With this release we have improved the help text that explains network volumes and how to use them within our solution. 43 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]] 35 35 36 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]] on the subject.{{/warning}} 45 +//__Debug queue__// 46 +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. 47 + 48 +[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]] 49 + 50 +== **Bug Fixes** == 51 +//__Internal server error__// 52 +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. 37 37 38 -== **Feedback items ** == 54 +//__Namespace update__// 55 +Editing a namespace used in a message definition automatically updates the message definition & transformations. 39 39 40 -//__ Removed OData as option foran API Gateway operation__//41 -W iththis release,wehaveremovedthe ODataoperation optionas itwasnotusedandwasnotfullysupportedanymorebytheplatform.57 +//__Error pop-up__// 58 +We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows. 42 42 43 -//__ ChangesinAPI Gatewayoperationpaths isautomaticallyupdatedin Create__//44 - Whenyou changeyourpath on a hostedAPIGateway we willnowautomaticallyupdate the accompanyingcomponentinyourCreate(all-)entry.60 +//__SMB inbound channel adapter__// 61 +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. 45 45 46 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}} 63 +//__Heap memory__// 64 +The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available. 47 47 48 -== **Bug fixes ** == 66 +//__Classpath conflicts__// 67 +We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. 49 49 50 -//__Prevent endless loop in Deploy -> User Management__// 51 -With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion. 52 - 53 -{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}} 54 - 55 -//__Update error handling during migration to the 3rd generation runtime__// 56 -As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration. 57 - 58 58 == **Fancy Forum Answers** == 59 59 60 60 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: 61 61 62 -* [[ Access Spring ApplicationContextwithinGroovyScript>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]63 -* [[ Configurationproblem: Failed to locate'$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]64 -* [[ 503onSOAPWebservicehostedineMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]73 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 74 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 75 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 65 65 66 -== **Key takeaways** ==77 +== **Key Takeaways** == 67 67 68 -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:79 +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: 69 69 70 70 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 71 71 * If you have feedback or ideas for us, talk to the Platypus 72 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 83 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 73 73 * Clear your browser cache (Ctrl + Shift + Del) 74 -* Check out the release notes [here] 85 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]] 75 75 * Start thinking about how the license tracker can aid your development 76 76 * Start thinking about major, minor, and patch 77 -* Upgrade to the latest build number 78 78 * Keep making great integrations 79 79 80 80 Let's stay in touch and till next time! ... ... @@ -82,6 +82,11 @@ 82 82 {{info}} 83 83 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 84 84 85 -~*~* Indicates a GEN3-only feature. 86 -{{/info}})))((({{toc/}}))){{/container}} 95 +{{/info}} 96 +))) 97 + 98 +((( 99 +{{toc/}} 100 +))) 87 87 {{/container}} 102 +{{/container}}