Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 266.1
edited by CarlijnKokkeler
on 2023/11/22 15:31
Change comment: There is no comment for this version
To version 600.1
edited by CarlijnKokkeler
on 2024/07/16 14:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +225 - TBD
Content
... ... @@ -3,71 +3,74 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
6 +**Hi there, eMagiz developers!**
7 7  
8 -{{warning}}
9 -Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10 -{{/warning}}
11 11  
12 -== **Quicker Deployment Plan Execution** ==
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.
13 13  
14 -We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. So, the deployment plan will be finished much quicker now!
13 +[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
15 15  
16 -== **Next Generation Architecture Default** ==
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.
17 17  
18 -With this release, the next generation architecture will become the default. From now on, new models will then use this generation as the default architecture.
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.
19 19  
20 -[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
21 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
21 21  
22 -== **Cloud Template R11 Docker - Single Lane** ==
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 23  
24 -This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
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.
25 25  
26 -== **Cloud Template R13 Docker - Double Lane** ==
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]]
27 27  
28 -This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
39 +//__Unused support objects__//
40 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
29 29  
30 -== **Feedback Items** ==
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.
31 31  
32 -//__Unused properties overview__//
33 -In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
47 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
34 34  
35 -* Not used by any runtime that is in the Create phase release.
36 -* Not required by a flow that is in the Create phase release.
37 -* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
38 -
39 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-unused-properties-overview.png]]
40 -
41 -//__Queue explorer milliseconds__//
42 -The queue browser now displays milliseconds in the timestamps.
43 -
44 -//__Unused images__//
45 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
46 -
47 -//__Carwash logging__//
48 -A new logging feature enabling us to make better choices in encryption standards will be released.
49 -
50 -//__Static alerts queue consumers__//
51 -Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
52 -
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 +
53 53  == **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.
54 54  
55 -//__Flow Designer connection line__//
56 -In the Flow Designer an issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
58 +//__Namespace update__//
59 +Editing a namespace used in a message definition automatically updates the message definition & transformations.
57 57  
58 -//__Portal for migrated models__//
59 -We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
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.
60 60  
61 -//__Error channel inbounds__//
62 -We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
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.
63 63  
64 64  == **Fancy Forum Answers** ==
65 65  
66 66  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:
67 67  
68 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
71 +* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
69 69  
70 -== **Key takeaways** ==
73 +== **Key Takeaways** ==
71 71  
72 72  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:
73 73  
... ... @@ -75,10 +75,9 @@
75 75  * If you have feedback or ideas for us, talk to the Platypus
76 76  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
77 77  * Clear your browser cache (Ctrl + Shift + Del)
78 -* Check out the release notes [here]
81 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
79 79  * Start thinking about how the license tracker can aid your development
80 80  * Start thinking about major, minor, and patch
81 -* Upgrade to the latest build number
82 82  * Keep making great integrations
83 83  
84 84  Let's stay in touch and till next time!
... ... @@ -86,7 +86,6 @@
86 86  {{info}}
87 87  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
88 88  
89 -~*~* Indicates a next-generation-architecture only feature.
90 90  {{/info}}
91 91  )))
92 92