Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40

From version 601.1
edited by CarlijnKokkeler
on 2024/07/16 14:28
Change comment: There is no comment for this version
To version 284.1
edited by CarlijnKokkeler
on 2023/12/04 15:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - TBD
1 +210 - Deployment Delights
Content
... ... @@ -3,82 +3,56 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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.
7 7  
8 +== **Alerts** ==
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 +//__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.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
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 +== **Feedback Items** ==
17 17  
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.
18 +//__Container version overview__//
19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
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 +//__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.
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 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
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:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
38 -
39 -//__Unused support objects__//
40 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
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.
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 -[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
53 -
54 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.
57 57  
58 -//__Namespace update__//
59 -Editing a namespace used in a message definition automatically updates the message definition & transformations.
31 +//__Runtime metrics processing__//
32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
60 60  
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.
34 +//__Deployment plan__//
35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
63 63  
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 LINK is available.
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.
66 66  
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 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.
69 69  
70 -//__Classpath conflicts__//
71 -We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
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.
72 72  
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 +
73 73  == **Fancy Forum Answers** ==
74 74  
75 75  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:
76 76  
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"]]
53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
80 80  
81 -== **Key Takeaways** ==
55 +== **Key takeaways** ==
82 82  
83 83  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:
84 84  
... ... @@ -86,9 +86,10 @@
86 86  * If you have feedback or ideas for us, talk to the Platypus
87 87  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
88 88  * Clear your browser cache (Ctrl + Shift + Del)
89 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
63 +* Check out the release notes [here]
90 90  * Start thinking about how the license tracker can aid your development
91 91  * Start thinking about major, minor, and patch
66 +* Upgrade to the latest build number
92 92  * Keep making great integrations
93 93  
94 94  Let's stay in touch and till next time!
... ... @@ -96,6 +96,7 @@
96 96  {{info}}
97 97  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
98 98  
74 +~*~* Indicates a next-generation-architecture only feature.
99 99  {{/info}}
100 100  )))
101 101