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 10- Deployment Delights1 +225 - TBD - Content
-
... ... @@ -3,56 +3,58 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several for the Store. Lastly, we made some changes to the alerts that you may be receiving.6 +**Hi there, eMagiz developers!** 7 7 8 -== **Alerts** == 9 9 10 -//__Topic approaching max size alert__// 11 -The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives. 9 +== **Feedback Items** == 10 +//__Alerting notification settings__// 11 +The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature. 12 12 13 -//__Missing metrics alert__// 14 -We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 13 +[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]] 15 15 16 -== **Feedback Items** == 15 +//__Process containers__// 16 +If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern. 17 17 18 -//__ Container versionoverview__//19 - InDeploy> Releases, itis nowpossibletoseethecontainerversions inthe releasedetails.Thiscanbeviewedbyclickingthethreedotsin theCreate phasesection.18 +//__Design settings__// 19 +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. 20 20 21 -[[image:Main.Images.Release Blog.WebHome@release- blog-210-deployment-delights-container-overview.png]]21 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]] 22 22 23 -//__Unchanged containers__// 24 -When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 23 +//__Untested images__// 24 + 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. 25 + 26 +[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]] 25 25 26 -//__Rebuilding of images__// 27 -Changing the list of flows that should run on a container will now trigger the rebuilding of images. 28 +//__Infinispan Cache Manager__// 29 +We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK 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 LINK is available. 28 28 29 -== **Bug Fixes** == 34 +//__Flow bump__// 35 +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. 36 + 37 +IMAGE 30 30 31 -//__ Runtimemetricsprocessing__//32 - Thecollectionandpublishingof runtimemetrics isnolongersynchronized across containers,which improvestheirprocessing.39 +//__Unused support objects__// 40 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'. 33 33 34 - //__Deploymentplan__//35 - Wesolved a bug where a deployment step in the deployment plan could randomly get stuck.42 +[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]] 43 + 36 36 37 -//__Store message merging__// 38 -The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages. 45 +== **Bug Fixes** == 39 39 40 -//__View all store items__// 41 -An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 42 42 43 -//__Out of memory behavior__// 44 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 45 45 46 -//__Max fetch size__// 47 -We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. 48 48 50 + 49 49 == **Fancy Forum Answers** == 50 50 51 51 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: 52 52 53 -* [[ JSONPathinSpELexpressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]55 +* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]] 54 54 55 -== **Key takeaways** ==57 +== **Key Takeaways** == 56 56 57 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: 58 58 ... ... @@ -60,10 +60,9 @@ 60 60 * If you have feedback or ideas for us, talk to the Platypus 61 61 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 62 62 * Clear your browser cache (Ctrl + Shift + Del) 63 -* Check out the release notes [here] 65 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]] 64 64 * Start thinking about how the license tracker can aid your development 65 65 * Start thinking about major, minor, and patch 66 -* Upgrade to the latest build number 67 67 * Keep making great integrations 68 68 69 69 Let's stay in touch and till next time! ... ... @@ -71,7 +71,6 @@ 71 71 {{info}} 72 72 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 73 73 74 -~*~* Indicates a next-generation-architecture only feature. 75 75 {{/info}} 76 76 ))) 77 77