Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 599.1
edited by CarlijnKokkeler
on 2024/07/16 14:12
Change comment: There is no comment for this version
To version 250.1
edited by CarlijnKokkeler
on 2023/11/21 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - TBD
1 +209 - Max Verstappen
Content
... ... @@ -1,70 +1,74 @@
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!**
5 +**Hi there, eMagiz developers!** We have done .....
7 7  
7 +{{warning}}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. {{/warning}}
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.
9 +== **Quicker Deployment Plan** ==
10 +We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now!
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
12 +== **Next Generation Architecture Default** ==
13 +With this release, the next generation architecture will become the default. New models will use this generation as default.
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.
15 +[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
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.
17 +== **Cloud Template R11 Docker - Single Lane** ==
18 +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.WebHome||target="blank"]].
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
20 +== **Cloud Template R13 Docker - Double Lane** ==
21 +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.WebHome||target="blank"]].
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 +== **Feedback Items** ==
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.
25 +//__Unused properties overview__//
26 +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:
27 +* Not used by any runtime that is in the Create phase release.
28 +* Not required by a flow that is in the Create phase release.
29 +* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
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]]
31 +//__Send build requests asynchronously__//
32 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
38 38  
39 -//__Unused support objects__//
40 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
34 +//__Queue explorer milliseconds__//
35 +The queue browser now displays milliseconds in the timestamps.
41 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.
37 +//__Cancel and next buttons order__//
38 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
40 +//__Unused images__//
41 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
48 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 -== **Bug Fixes** ==
43 +//__Carwash logging__//
44 +A new logging feature enabling us to make better choices in encryption standards will be released.
55 55  
46 +//__Static alerts queue consumers__//
47 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
56 56  
49 +== **Bug Fixes** ==
57 57  
51 +//__Flow Designer connection line__//
52 +In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
58 58  
54 +//__Portal for migrated models__//
55 +We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
59 59  
57 +//__Error channel inbounds__//
58 +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.
59 +
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  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:
63 63  
64 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
64 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
65 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
66 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
67 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
65 65  
66 -== **Key Takeaways** ==
67 67  
70 +== **Key takeaways** ==
71 +
68 68  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:
69 69  
70 70  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -71,9 +71,10 @@
71 71  * If you have feedback or ideas for us, talk to the Platypus
72 72  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
73 73  * Clear your browser cache (Ctrl + Shift + Del)
74 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
78 +* Check out the release notes [here]
75 75  * Start thinking about how the license tracker can aid your development
76 76  * Start thinking about major, minor, and patch
81 +* Upgrade to the latest build number
77 77  * Keep making great integrations
78 78  
79 79  Let's stay in touch and till next time!
... ... @@ -81,11 +81,6 @@
81 81  {{info}}
82 82  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83 83  
84 -{{/info}}
85 -)))
86 -
87 -(((
88 -{{toc/}}
89 -)))
89 +~*~* Indicates a next-generation-architecture only feature.
90 +{{/info}})))((({{toc/}}))){{/container}}
90 90  {{/container}}
91 -{{/container}}