Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 603.1
edited by Erik Bakker
on 2024/07/16 14:38
Change comment: There is no comment for this version
To version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - Pop-up Party
1 +199 - Home Improvements
Content
... ... @@ -1,90 +1,58 @@
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!** 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!
5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
7 7  
8 -== **Feedback Items** ==
9 -//__Alerting notification settings__//
7 +== **Next generation improvements and bug fixes** ==
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.
9 +//__Enhanced overview of the HTTP Statistics__//
10 +As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
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.
12 +//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13 +In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
15 +{{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}}
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]]
17 +//__Forced congestion control__//
18 +To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
23 23  
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.
29 29  
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]]
21 +//__Improved validation errors on the invalid configuration of HTTP outbound components__//
22 +This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
34 34  
35 -//__Unused support objects__//
36 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
24 +//__Improved migration behavior__//
25 +This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
26 +A smoother migration of your JMS (and backup JMS) process.
27 +Shortening of names that otherwise would be too long, additional feedback given to the user.
28 +Feedback when the migration process is finished.
37 37  
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.
30 +//__Additional checks when deploying__//
31 +This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
42 42  
43 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
33 +== **Store Improvements** ==
44 44  
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.
35 +== **Event Streaming - Certificate Management** ==
53 53  
54 -//__Namespace update__//
55 -Editing a namespace used in a message definition automatically updates the message definition & transformations.
56 -
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.
59 -
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.
62 -
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.
65 -
66 -//__Classpath conflicts__//
67 -We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
68 -
69 69  == **Fancy Forum Answers** ==
70 70  
71 71  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:
72 72  
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"]]
41 +* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
42 +* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
76 76  
77 -== **Key Takeaways** ==
44 +== **Key takeaways** ==
78 78  
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:
46 +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:
80 80  
81 81  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
82 82  * If you have feedback or ideas for us, talk to the Platypus
83 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
50 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
84 84  * Clear your browser cache (Ctrl + Shift + Del)
85 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
52 +* Check out the release notes [here]
86 86  * Start thinking about how the license tracker can aid your development
87 87  * Start thinking about major, minor, and patch
55 +* Upgrade to the latest build number
88 88  * Keep making great integrations
89 89  
90 90  Let's stay in touch and till next time!
... ... @@ -92,11 +92,6 @@
92 92  {{info}}
93 93  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
94 94  
95 -{{/info}}
96 -)))
97 -
98 -(((
99 -{{toc/}}
100 -)))
63 +~*~* Indicates a GEN3-only feature.
64 +{{/info}})))((({{toc/}}))){{/container}}
101 101  {{/container}}
102 -{{/container}}