Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 120.1
edited by Erik Bakker
on 2025/01/31 11:52
Change comment: There is no comment for this version
To version 119.2
edited by Erik Bakker
on 2025/01/31 11:46
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -237.1 - Fabulous Flow
1 +2371 - Fabulous Flow
Content
... ... @@ -1,6 +1,9 @@
1 -This release signifies our efforts to stabilize containers running on-premise on Windows as part of our [[announced hotfix>>https://status.emagiz.com/incidents/h3kftq4wpg3n||target="blank"]]. It consists of a revert of our announced functionality regarding Windows memory limits.
1 +This release signifies our efforts to stabilize the management of our customer models from Manage even better. It consists of several much-needed functionalities for specific use cases regarding the next-generation architecture.
2 2  
3 -====Reverts====
3 +====Minor changes====
4 4  
5 -* Deploy - Architecture: To prevent out-of-memory events, the calculation of each runtime's memory limit is updated for all runtimes deployed on a Windows machine.
5 +* Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80%
6 +* Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (Gen3 only)
7 +* Manage - Queue statistics: They are now all visible for models with a vast number of queues. This used to be cut off. (Gen3 only)
8 +* Manage - Monitoring: Removed time filter options for time windows longer than the last seven days in 3rd generation runtime statistics dashboards.
6 6