Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 232.1
edited by Carlijn Kokkeler
on 2023/10/24 16:10
Change comment: There is no comment for this version
To version 234.1
edited by Carlijn Kokkeler
on 2023/10/25 14:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,12 +2,10 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection.
5 +**Hi there, eMagiz developers!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection. Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
6 6  
7 7  {{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
8 8  
9 -Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
10 -
11 11  == **State Generation~*~*** ==
12 12  
13 13  //__New components__//
... ... @@ -88,11 +88,11 @@
88 88  //__System alignment__//
89 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.
90 90  
91 -//__Error checking__//
89 +//__Error alerting__//
92 92  The error trigger is now configured to check if an error message contains a certain term, besides checking the error header.
93 93  
94 94  //__Alerting__//
95 -For the next generation architecture models, several adaptations to alerts have been made.
93 +For the next generation architecture models, several adaptations to triggers have been made.
96 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 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 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.