Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
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 82.1
edited by Erik Bakker
on 2023/02/14 14:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +192 - Small Step
Content
... ... @@ -2,55 +2,56 @@
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 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.
5 +**Hi there, eMagiz developers!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have a new event streaming graph and some updates to our platform in general.
6 6  
7 -== **Event streaming alerting** ==
7 +== **Start/Stop Flows** ~*~* ==
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.
9 +{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
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.
11 +To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
12 12  
13 -The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
13 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
15 +After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start.
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.
17 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
19 +{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
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.
21 +== **Manage overview Event Streaming** ~*~* ==
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"]].
23 +To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data.
24 24  
25 -== **3rd generation improvements** ==
25 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
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.
27 +== **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.
29 +We have also solved other feedback items besides the flow designer's critical updates.
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.
31 +//__Topic configuration calculation__//
32 +With this release we have simplified the configuration of settings on topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics.
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.
34 +//__Make preparation step in deployment plan visible__//
35 +For a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan.
38 38  
39 -== **Feedback items ** ==
37 +{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
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.
39 +//__3rd generation runtime debugger feedback__//
40 +We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
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.
42 +//__No "Shift key" needed anymore to select multiple items in the flow designer__//
43 +As of now you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
46 46  
45 +//__User Management synchronization now happens in one step__//
46 +With this release we have updated the synchronization process between Design and Deploy with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized.
47 +
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"]]
52 +* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
53 +* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
54 +* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
54 54  
55 55  == **Key takeaways** ==
56 56