Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 139.1
edited by Carlijn Kokkeler
on 2023/10/23 16:48
Change comment: There is no comment for this version
To version 305.1
edited by Carlijn Kokkeler
on 2024/08/26 14:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +228 - Monitoring Mania
Content
... ... @@ -1,20 +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 +During our recent sprint cycle, w...
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.228 - Monitoring Mania||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +====Minor changes====
6 +* Community - Release Notes: The legacy release notes tab has been removed.
7 +* Create - Flow Testing: Test messages can now be edited or removed while in the edit mode of the flow testing functionality.
8 +* Deploy - Architecture: The SSL section in runtime settings has more elaborate helptext.
9 +* Deploy - Architecture: A pop-up with a warning will be shown when containers are configured with less memory than recommended.
10 +* Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.
11 +* Deploy - History: We added logging for when properties are deleted from the unused properties screen.
12 +* Deploy - Missing Properties Overview: Setting the value of a missing property will now automatically remove it from the missing properties overview. Besides that, search and sort functionality have been added to the missing properties overview.
13 +* Manage - Monitoring: We have done many improvements to the Monitoring graphs. Find out all improvements in our [[release blog>>Main.Release Information.Release Blogs.228 - Monitoring Mania||target="blank"]]. (#866)
6 6  
7 -* 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.
8 -* Design - Message Mapping: The button 'Import from Store' will directly open the store.
9 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking.
10 -* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
11 -
12 12  ====Bug fixes====
13 -
14 -* 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.
15 -
16 -
17 -
18 -=====Infra and image changes=====
19 -
20 -* 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.
16 +* Create - Flow Designer: We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production. (#1065)
17 +* Create - Flow Designer: The copy paste functionality in the flow designer does not change the configuration of existing flow components anymore. (#1392)
18 +* Create - Flow Testing: It is now possible to reuse the test messages from the onramp in the routing and vice versa in flow testing. (#1274)
19 +* Deploy - Architecture: We fixed a bug where new machines could be deployed with exceeding memory. (#1295)