Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 113.1
edited by Erik Bakker
on 2023/05/09 12:59
Change comment: There is no comment for this version
To version 254.1
edited by Carlijn Kokkeler
on 2023/11/21 12:04
Change comment: Renamed back-links.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,64 +1,83 @@
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!** In the last few weeks, we have work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
6 +**Hi there, eMagiz developers!** We have done .....
6 6  
7 -== **Event streaming alerting** ==
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}}
8 8  
9 -With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it.
12 +== **Quicker Deployment Plan** ==
10 10  
11 -The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication that messages might be deleted before consumer groups had the option to consume the messages.
14 +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 -The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
16 +== **Next Generation Architecture Default** ==
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
18 +With this release, the next generation architecture will become the default. New models will use this generation as default.
16 16  
17 -The first new "dynamic" alert allows you to raise an alert once the total number of messages on one (or more topics) is less than a certain number per defined time unit. So for example you can configure an alert once the number of message placed on a topic called "Exception" is less than 15 messages within 5 minutes.
20 +[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
22 +== **Cloud Template R11 Docker - Single Lane** ==
20 20  
21 -The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
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"]].
22 22  
23 -For more information on the generic way of working surrounding alerting please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
26 +== **Cloud Template R13 Docker - Double Lane** ==
24 24  
25 -== **3rd generation improvements** ==
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"]].
26 26  
27 -//__Increased grace period for shutdown__//
28 -In this release, we have increased the grace period a container gets to shutdown before it is forcefully shutdown. This should reduce the chance of unwanted failover behavior to pop-up within your model.
30 +== **Feedback Items** ==
29 29  
30 -//__Update at once or not__//
31 -This release fixes 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.
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:
32 32  
33 -//__Improved user feedback while executing a deployment plan__//
34 -This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information of why this cannot be executed is shown to the user. This way they can take this information and act upon it instead of assuming everything went well.
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.
35 35  
36 -//__Improved auto-healing when running in a hybrid situation__//
37 -In situations where you run in a hybrid situation (i.e. partly next-gen and partly the current generation) we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next generation architecture.
39 +//__Send build requests asynchronously__//
40 +The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
38 38  
39 -== **Feedback items ** ==
42 +//__Queue explorer milliseconds__//
43 +The queue browser now displays milliseconds in the timestamps.
40 40  
41 -//__Make sure the message format can be viewed without "Start editing"__//
42 -With this release, we have ensured that when you navigate to Design -> System message you can see the message format (i.e. XML, JSON or EDI) without entering the "Start Editing" mode.
45 +//__Cancel and next buttons order__//
46 +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.
43 43  
44 -//__Various styling improvements in the flow testing functionality__//
45 -Various smaller styling improvements have been added to the flow testing functionality to improve the overall user experience. For a complete list and more details please check out the release notes.
48 +//__Unused images__//
49 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
46 46  
51 +//__Carwash logging__//
52 +A new logging feature enabling us to make better choices in encryption standards will be released.
53 +
54 +//__Static alerts queue consumers__//
55 +Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
56 +
57 +== **Bug Fixes** ==
58 +
59 +//__Flow Designer connection line__//
60 +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.
61 +
62 +//__Portal for migrated models__//
63 +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.
64 +
65 +//__Error channel inbounds__//
66 +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.
67 +
47 47  == **Fancy Forum Answers** ==
48 48  
49 49  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:
50 50  
51 -* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
52 -* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
53 -* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
72 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
54 54  
55 55  == **Key takeaways** ==
56 56  
57 -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:
76 +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:
58 58  
59 59  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
60 60  * If you have feedback or ideas for us, talk to the Platypus
61 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
62 62  * Clear your browser cache (Ctrl + Shift + Del)
63 63  * Check out the release notes [here]
64 64  * Start thinking about how the license tracker can aid your development
... ... @@ -71,6 +71,12 @@
71 71  {{info}}
72 72  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73 73  
74 -~*~* Indicates a GEN3-only feature.
75 -{{/info}})))((({{toc/}}))){{/container}}
93 +~*~* Indicates a next-generation-architecture only feature.
94 +{{/info}}
95 +)))
96 +
97 +(((
98 +{{toc/}}
99 +)))
76 76  {{/container}}
101 +{{/container}}