Changes for page 226 - Alerting Alchemy
Last modified by Carlijn Kokkeler on 2024/07/29 14:01
From version 200.1
edited by Carlijn Kokkeler
on 2024/02/16 12:08
on 2024/02/16 12:08
Change comment:
There is no comment for this version
To version 211.1
edited by Carlijn Kokkeler
on 2024/03/25 12:29
on 2024/03/25 12:29
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 4-SystemSymphony1 +217 - Template Tango - Content
-
... ... @@ -1,21 +1,17 @@ 1 -In the last sprint cycle, we focused on impro vingfailover aspects. Moreover, weimprovedthehistoryof monitoringgraphs, itisnow possibleoviewdatafrom upto thelast thirty days. Lastly,somemore feedbackitemshavebeensolved, andseveralmorebug fixeshavebeendone.1 +In the last sprint cycle, we focused on delivering new cloud templates for docker single and docker double lane. Moreover, we have added clipboard buttons to several pages, and migrated the generic alert trigger "More than 100 messages on queue over 10 minutes" to a custom trigger. Lastly, we enabled the removal of eMagiz infra H2 databases for connector machines, and improved the checks on the runtime versions in the runtime overview. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.21 4-SystemSymphony||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.217 - Template Tango||target="blank"]]. 4 4 5 5 =====New features===== 6 6 7 -* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once. (#1141) 8 -* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. 7 +* Create - Flow Designer & Deploy: Copy to clipboard buttons have been added to various pages. 8 +* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce the ability to clean H2 databases from the portal. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 9 +* Manage - Alerting: The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger. 9 9 10 10 =====Minor changes===== 11 11 12 -* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore. (#1216) 13 -* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days. 13 +* Deploy - Architecture: For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note that only H2 databases that are registered under the standard eMagiz data folder will be removed. Moreover, it is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. Lastly, for on-premise runtimes, only a reset of the runtime is needed. 14 14 15 15 ====Bug fixes==== 16 16 17 -* Create - Flow Designer: The help text of the Group attribute has been improved. 18 -* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802) 19 -* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed. 20 - 21 - 17 +* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)