Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 606.1
edited by CarlijnKokkeler
on 2024/07/16 14:43
Change comment: There is no comment for this version
To version 290.1
edited by CarlijnKokkeler
on 2023/12/06 14:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - Pop-up Party
1 +210 - Deployment Delights
Content
... ... @@ -3,85 +3,62 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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!
6 +**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7 7  
8 -== **Feedback Items** ==
9 -//__Alerting notification settings__//
8 +== **Alerts** ==
10 10  
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.
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
13 13  
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.
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
16 +== **Feedback Items** ==
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}}
18 +//__Improved release build process__//
19 +When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
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.
21 +//__Container version overview__//
22 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
35 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]]
24 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
40 40  
41 -//__Unused support objects__//
42 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
26 +//_Improved deployment process_//
27 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
43 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.
29 +//__Rebuilding of images__//
30 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
48 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 -//__Namespace update__//
61 -Editing a namespace used in a message definition automatically updates the message definition & transformations.
34 +//__Runtime metrics processing__//
35 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
62 62  
63 -//__Error pop-up__//
64 -We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
37 +//__Deployment plan__//
38 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
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.
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.
68 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.
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.
71 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.
46 +//__Max fetch size__//
47 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
74 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"]]
53 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
82 82  
83 -== **Key Takeaways** ==
84 84  
60 +== **Key takeaways** ==
61 +
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,9 +88,10 @@
88 88  * If you have feedback or ideas for us, talk to the Platypus
89 89  * 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"]]
68 +* 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
71 +* 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,6 +98,7 @@
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  
79 +~*~* Indicates a next-generation-architecture only feature.
101 101  {{/info}}
102 102  )))
103 103