Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
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 87.1
edited by Erik Bakker
on 2023/06/06 08:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +199 - Home Improvements
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,27 +1,19 @@
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 improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, the store, security, and certificate management.
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.199 - Home Improvements.WebHome||target= "blank"]].
4 4  
5 5  =====Minor changes=====
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-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
8 +* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899)
9 +* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately three months before event streaming users' access certificates expire.
10 +* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan.
11 +* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960)
12 +* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.
13 +* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.
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.
17 +* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864)
18 +* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937)
22 22  
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.