Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 598.1
edited by CarlijnKokkeler
on 2024/07/16 14:03
on 2024/07/16 14:03
Change comment:
There is no comment for this version
To version 128.1
edited by Erik Bakker
on 2023/07/17 14:47
on 2023/07/17 14:47
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-TBD1 +201 - Be Informed - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,77 +1,70 @@ 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!** 5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you. 7 7 7 +== **Announcement - Release Properties** == 8 +As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 8 8 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. 10 +== ** Deploy Architecture - Apply To Environment improvements ** == 11 +As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]] 13 +//__Enhanced right-hand view within Deployment Plan context__// 14 +When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview. 14 14 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. 16 +{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}} 17 17 18 -//__ Designsettings__//19 - WhenpressingApplysettingsinDesignSettings,aconfirmationscreenwillnowbeshowntopresentthe changesthatwill betakeninto effectfor each environment.18 +//__Improved timeout settings when deploying__// 19 +To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur. 20 20 21 - [[image:Main.Images.ReleaseBlog.WebHome@release-225-design-settings.png]]21 +{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 22 22 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]] 23 +//__Detailed HTTP Statistics now show user info in specific additional cases__// 24 +To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations. 27 27 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. 26 +{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 33 33 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 28 +//__Improved loading speed of Manage Dashboard__// 29 +This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase. 38 38 39 -//__Unused support objects__// 40 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'. 31 +== **Store Improvements** == 41 41 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. 33 +//__Importing in Design is improved__// 34 +We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create. 46 46 47 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]] 48 - 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 52 == **Bug Fixes** == 53 53 38 +//__Deprecated reminder pop-up removed__// 39 +We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems. 54 54 41 +//__Improved selection area in Flow Designer__// 42 +When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow. 55 55 44 +//__Improved Kafka settings__// 45 +For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them. 56 56 47 +{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}} 57 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 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]] 53 +* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]] 54 +* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]] 63 63 64 -== **Key Takeaways** ==56 +== **Key takeaways** == 65 65 66 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:58 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 67 67 68 68 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 69 69 * If you have feedback or ideas for us, talk to the Platypus 70 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 62 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 71 71 * Clear your browser cache (Ctrl + Shift + Del) 72 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]64 +* Check out the release notes [here] 73 73 * Start thinking about how the license tracker can aid your development 74 74 * Start thinking about major, minor, and patch 67 +* Upgrade to the latest build number 75 75 * Keep making great integrations 76 76 77 77 Let's stay in touch and till next time! ... ... @@ -79,11 +79,6 @@ 79 79 {{info}} 80 80 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 81 81 82 -{{/info}} 83 -))) 84 - 85 -((( 86 -{{toc/}} 87 -))) 75 +~*~* Indicates a GEN3-only feature. 76 +{{/info}})))((({{toc/}}))){{/container}} 88 88 {{/container}} 89 -{{/container}}