Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 112.1
edited by Carlijn Kokkeler
on 2023/10/11 12:53
Change comment: There is no comment for this version
To version 141.1
edited by Carlijn Kokkeler
on 2023/10/23 16:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +207 - Aligned State
Content
... ... @@ -1,26 +1,29 @@
1 -In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
4 4  
5 -=====New features=====
6 -
7 -* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
8 -
9 9  =====Minor changes=====
10 10  
11 -* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
12 -* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
13 -* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052)
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%.
15 +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%.
16 +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.
17 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
18 +* 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)
14 14  
15 -
16 16  ====Bug fixes====
17 17  
18 -* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
19 -* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
20 -* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
21 -* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
22 +* 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)
23 +* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
22 22  
23 23  
26 +
24 24  =====Infra and image changes=====
25 25  
26 -* No infra and/or image changes is this release.
29 +* 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.