Skip to Content

Changes for page 198 - Great Migration

Last modified by Carlijn Kokkeler on 2024/04/18 13:14
From version 114.1
edited by Erik Bakker
on 2023/05/09 13:41
Change comment: There is no comment for this version
To version 116.1
edited by Erik Bakker
on 2023/05/10 08:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,7 +16,7 @@
16 16  
17 17  The first new "dynamic" alert allows you to raise an alert once the 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 messages placed on a topic called "Exception" is less than 15 messages within 5 minutes.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
19 +[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
20 20  
21 21  The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups are more than X messages behind on one or more topics. The configuration of this is comparable to what we saw before.
22 22  
... ... @@ -36,6 +36,11 @@
36 36  //__Improved auto-healing when running in a hybrid situation__//
37 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.
38 38  
39 +//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
40 +To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
41 +
42 +{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
43 +
39 39  == **Feedback items ** ==
40 40  
41 41  //__Make sure the message format can be viewed without "Start editing"__//