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 151.1
edited by Erik Bakker
on 2023/09/13 07:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - Pop-up Party
1 +205 - World Explorers
Content
... ... @@ -1,80 +1,62 @@
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!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
7 7  
8 -== **Feedback Items** ==
9 -//__Alerting notification settings__//
7 +== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
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 +As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
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.
11 +== **Feedback Items** ==
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
13 +//__Improved Validation when migrating to the next-generation architecture__//
14 +To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
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]]
16 +{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
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.
18 +//__Improved HTTP Statistics__//
19 +To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
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 +//__"Topic Full" alert restriction changed__//
22 +With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better.
34 34  
35 -//__Unused support objects__//
36 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
24 +//__Improved performance Manage Dashboards__//
25 +We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
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.
27 +//__Show values on the runtime level in Deploy Architecture__//
28 +We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
42 42  
43 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
30 +{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
31 +* JMS - The number of queues in the active release.
32 +* Messaging Container - The number of messaging integrations in the active release.
33 +* Messaging Connector - The number of messaging integrations related to this system in the active release.
34 +* API Gateway Container - The number of operations in the active release.
35 +* Event Streaming Container - The number of event processors in the active release.
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 -
37 +There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
38 +
50 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.
53 53  
54 -//__Namespace update__//
55 -Editing a namespace used in a message definition automatically updates the message definition & transformations.
41 +//__Improved information Queue Statistics__//
42 +Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release.
56 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.
44 +//__Gain the ability again to configure certificates in Deploy Architecture again__//
45 +In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
59 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.
47 +//__Ensure that differing container configurations deploy the correct configuration__//
48 +When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
62 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.
50 +//__Remove queurying options in Manage__//
51 +To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
65 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"]]
57 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
76 76  
77 -== **Key Takeaways** ==
59 +== **Key takeaways** ==
78 78  
79 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:
80 80  
... ... @@ -82,9 +82,10 @@
82 82  * If you have feedback or ideas for us, talk to the Platypus
83 83  * 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"]]
67 +* 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
70 +* 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 -)))
78 +~*~* Indicates a next-generation-architecture only feature.
79 +{{/info}})))((({{toc/}}))){{/container}}
101 101  {{/container}}
102 -{{/container}}