Skip to Content

Changes for page 198 - Great Migration

Last modified by Carlijn Kokkeler on 2024/04/18 13:14
From version 112.1
edited by Erik Bakker
on 2023/05/09 12:45
Change comment: There is no comment for this version
To version 109.1
edited by Erik Bakker
on 2023/05/05 10:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +196 - The Last Post
Content
... ... @@ -2,26 +2,24 @@
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 few weeks, we have work hard on improving our next generation architecture and introduced the "live" mode within our flow testing functionality. Furthermore there are loads of 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 -== **Event streaming alerting** ==
7 +== **"Live" mode on flow testing** ==
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 +With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch between "live" and "mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all external communication is mocked by the system and only the functional process can be tested.
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 +By switching to "live" mode you can not only test the functional process but also the communication to the external system. You can do so by entering the "edit" mode of the flow test and toggle between "mock" and "live" mode. When doing so eMagiz will show you the following pop-up stressing the consequences of your actions.
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@196-release-blog--live-flow-testing-pop-up.png]]
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
15 +Once confirmed you will see that the user interface now indicates that the endpoint is in "live" mode.
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@196-release-blog--live-flow-testing-result.png]]
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
19 +{{info}}* The following restrictions apply for this functionality
20 + ** "Live" mode can only be activated on HTTP outbound gateway components
21 + ** "Live" mode can **not** be active when you want to use the flow test as an "automated" test{{/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.
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"]].
24 -
25 25  == **3rd generation improvements** ==
26 26  
27 27  //__Event Streaming statistics completion__//