Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 230.1
edited by Carlijn Kokkeler
on 2023/10/24 16:04
Change comment: There is no comment for this version
To version 223.1
edited by Carlijn Kokkeler
on 2023/10/24 11:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -30,8 +30,6 @@
30 30  
31 31  {{info}}The components are all configurable from the Flow Designer in Create and are accompanied by a help text explaining the use cases and the various technical configurations. Note that to make the components work in your model, a new release containing the latest image (2.0.0) needs to be deployed.{{/info}}
32 32  
33 -{{warning}}The library used for Code Mappings has been changed. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0. This has no consequences on a functional level. {{/warning}}
34 -
35 35  == **Metrics Storage Duration** ==
36 36  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 7, 14 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.
37 37  
... ... @@ -86,16 +86,15 @@
86 86  The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
87 87  
88 88  //__System alignment__//
89 -The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases. This will be done for existing systems as well.
87 +The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases.
90 90  
91 91  //__Error checking__//
92 -The error trigger is now configured to check if an error message contains a certain term, besides checking the error header.
90 +Besides checking error header, the error trigger is now configured to check if an error message contains a term.
93 93  
94 94  //__Alerting__//
95 -For the next generation architecture models, several adaptations to alerts have been made.
96 -* For the next generation architecture models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
97 -* For the next generation architecture 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%.
98 -* The next generation architecture 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.
93 +For the next generation architecture models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
94 +For the next generation architecture 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%.
95 +The next generation architecture 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.
99 99  
100 100  //__Unused containers__//
101 101  Containers are set inactive when they are unused and removed in Design.