Skip to Content

Changes for page 215 - Tiny Tales

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
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 189.1
edited by Carlijn Kokkeler
on 2024/01/15 16:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +212 - Failover Fiesta
Content
... ... @@ -1,27 +1,16 @@
1 -In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
1 +In the last sprint cycle, we focused on providing new cloud templates that improve auto-healibng. Moreover, components and deployment steps have been created to support a failover setup. Lastly, bug fixes regarding message mapping and topic data models have been done.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +=====New features=====
6 6  
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)
11 -* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
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)
7 +* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
8 +* Create - Flow Designer: New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
9 +* Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
17 17  
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.
13 +* Design - Message Mapping: The message merging tool has been fixed to allow merging a store item message model into your own message models.
14 +* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements.
22 22  
23 23  
24 -
25 -=====Infra and image changes=====
26 -
27 -* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.