Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 09:59

From version 142.1
edited by Carlijn Kokkeler
on 2023/10/23 16:55
Change comment: There is no comment for this version
To version 140.1
edited by Carlijn Kokkeler
on 2023/10/23 16:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,21 +4,17 @@
4 4  
5 5  =====Minor changes=====
6 6  
7 +* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively.
7 7  * Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 -* Design - Performance: Performance improvements for the Flow Designer have been implemented.
9 -* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
10 -* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
9 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking.
11 11  * Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
12 12  * Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
13 -* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946)
14 -* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
15 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
16 -* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
17 17  
13 +
14 +
18 18  ====Bug fixes====
19 19  
20 -* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
21 -* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
17 +* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable.
22 22  
23 23  
24 24