Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 17.1
edited by eMagiz
on 2022/10/13 09:28
Change comment: There is no comment for this version
To version 603.1
edited by Erik Bakker
on 2024/07/16 14:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - Get ready
1 +225 - Pop-up Party
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -1,64 +1,102 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
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!
6 6  
7 -==**Audit trail User Management**==
8 -Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
8 +== **Feedback Items** ==
9 +//__Alerting notification settings__//
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.
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.
16 +
17 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
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.
9 9  
10 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
22 +[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
11 11  
12 -==**Next Generation Monitoring & Alerting engine**==
13 -In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
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.
14 14  
15 -* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
16 -* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
17 -* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
18 -* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
19 -* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
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 +
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.
20 20  
33 +[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
34 +
35 +//__Unused support objects__//
36 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
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.
42 +
43 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
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.
21 21  
22 -=== **Improvements** ===
23 -
24 -* Performance Deployment plan
25 -When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
26 -
27 -* Flow Designer updates
28 -We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
29 -
30 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
31 -
32 -* Store
33 -We have fixed several smaller Store import issues to improve the user experience.
34 -
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.
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 +
35 35  == **Fancy Forum Answers** ==
36 36  
37 -As always, a gentle reminder to all 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:
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:
38 38  
39 -* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
40 -* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
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 41  
42 -== **Key takeaways** ==
77 +== **Key Takeaways** ==
43 43  
44 -Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
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:
45 45  
46 46  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
47 47  * If you have feedback or ideas for us, talk to the Platypus
48 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
83 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49 49  * Clear your browser cache (Ctrl + Shift + Del)
50 -* Check out the release notes [here]
85 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
51 51  * Start thinking about how the license tracker can aid your development
52 52  * Start thinking about major, minor, and patch
53 -* Upgrade to the latest build number
54 54  * Keep making great integrations
55 -* Check out the new documentation portal.
56 56  
57 57  Let's stay in touch and till next time!
58 58  
59 59  {{info}}
60 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
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]]
61 61  
62 -~*~* Indicates a GEN3-only feature.
63 -{{/info}})))((({{toc/}}))){{/container}}
95 +{{/info}}
96 +)))
97 +
98 +(((
99 +{{toc/}}
100 +)))
64 64  {{/container}}
102 +{{/container}}