Skip to Content

Changes for page 192 - Small Step

Last modified by Carlijn Kokkeler on 2024/05/22 13:42
From version 51.1
edited by Erik Bakker
on 2023/02/17 08:05
Change comment: There is no comment for this version
To version 53.1
edited by Carlijn Kokkeler
on 2024/05/22 13:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -2,11 +2,11 @@
2 2  
3 3  Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.192 - Small Step.WebHome||target= "blank"]].
4 4  
5 -=====New features=====
5 +====New features====
6 6  * Deploy - Architecture: We add a new option per container to open a page that you can use a feature "Start / Stop flows" for runtime running on the 3rd generation runtime. Note that the debugger functionality can also be started on this view.
7 7  * Manage - Monitoring: New dashboard, ‘Event streaming statistics,’ is available for you to monitor your topics and consumer groups.
8 8  
9 -=====Minor changes=====
9 +====Minor changes====
10 10  
11 11  * Design- Kafka topic: As a user, you can now only define the retention size on the topic level. Based on that input value and a set of best practices eMagiz will, in turn, calculate the correct settings for you. Don't hesitate to contact your partner manager if you want to change the default settings. When applying the configured settings to your topic, we also send configuration settings for segment bytes and segment ms based on our best practice to improve performance.
12 12  * Create - Flow Designer: You can make a multiple selection zone by pressing and holding the left mouse button instead of pressing the "Shift" key from now on.
... ... @@ -15,6 +15,7 @@
15 15  
16 16  ====Bug fixes====
17 17  
18 +* Create - Flow Designer: We applied a new settings for the jms flow where the jms flow will try to shrink the journal files to 50 so it does not end up with a high amount of jms files which take too long to read. For this to be applied please reset your jms flow and deploy the new version on your bus.
18 18  * Deploy/Monitoring - Debugger: We have improved the error handling on the debugger functionality to ensure it does not show the error code and technical error anymore.
19 19  * Deploy/Monitoring - Debugger: Pressing the "Stop debugger" button now functions correctly
20 20