Skip to Content

Changes for page 198 - Great Migration

Last modified by Carlijn Kokkeler on 2024/04/18 13:14
From version 90.1
edited by Erik Bakker
on 2023/03/14 06:51
Change comment: There is no comment for this version
To version 113.1
edited by Erik Bakker
on 2023/05/09 12:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Big Leap
1 +197 - Pay Attention
Content
... ... @@ -2,66 +2,55 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
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 6  
7 -== **3rd generation improvements** ==
7 +== **Event streaming alerting** ==
8 8  
9 -//__Better feedback in error log when a corrupt stylesheet is encountered__//
10 -We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
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.
11 11  
12 -//__Better internal error handling to avoid unnecessary alerting and notifications__//
13 -We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
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 14  
15 -//__Improved Manage Dashboard__//
16 -This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
13 +The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
17 17  
18 -//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 -When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
15 +[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
20 20  
21 -//__Improved process of deploy preparation__//
22 -With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
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.
23 23  
24 -//__Improved migration of Streaming container__//
25 -When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
19 +[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
26 26  
27 -//__Add History to Notifications in Manage__//
28 -To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
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.
29 29  
30 -//__Improved Manage phase for Event Streaming__//
31 -Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
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"]].
32 32  
33 -//__Improved help text for network volumes__//
34 -With this release we have improved the help text that explains network volumes and how to use them within our solution.
25 +== **3rd generation improvements** ==
35 35  
36 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]] on the subject.{{/warning}}
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.
37 37  
38 -== **Feedback items ** ==
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.
39 39  
40 -//__Removed OData as option for an API Gateway operation__//
41 -With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
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.
42 42  
43 -//__Changes in API Gateway operation paths is automatically updated in Create__//
44 -When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
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.
45 45  
46 -{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
39 +== **Feedback items ** ==
47 47  
48 -== **Bug fixes ** ==
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.
49 49  
50 -//__Prevent endless loop in Deploy -> User Management__//
51 -With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
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.
52 52  
53 -{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
54 -
55 -//__Update error handling during migration to the 3rd generation runtime__//
56 -As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
57 -
58 58  == **Fancy Forum Answers** ==
59 59  
60 60  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:
61 61  
62 -* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
63 -* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
64 -* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
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"]]
65 65  
66 66  == **Key takeaways** ==
67 67