Changes for page 232 - Bug Busters
Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 184.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
on 2024/01/15 14:46
Change comment:
There is no comment for this version
To version 282.1
edited by Carlijn Kokkeler
on 2024/07/29 13:59
on 2024/07/29 13:59
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 -2 12 -FailoverFiesta1 +226 - Alerting Alchemy - Content
-
... ... @@ -1,27 +1,12 @@ 1 - Inthelast sprint cycle, wefocused on....1 +During our recent sprint cycle, we have worked to release .. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 12 -Feedback Fiesta||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.226 - Alerting Alchemy||target="blank"]]. 4 4 5 -=====New features===== 6 - 7 -* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines. 8 -* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 9 - 10 -=====Minor changes===== 11 - 12 -* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 13 -* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment. 14 -* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high. 15 -* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917) 16 -* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards. 17 -* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. 18 - 19 -====Bug fixes==== 20 - 21 -* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. 22 -* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks. 23 -* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 24 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container. 25 -* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108) 26 - 27 - 5 +====Minor changes==== 6 +* Create - Flow Designer: The Infinispan Cache Manager has been updated to provide an additional 'transport type' to offer more means for creating a clustered setup, provide clearer helptexts, and include validation on fields depending on the selected 'transport type'. 7 +* Design - Tenant: The technical name of a tenant cannot be changed once the tenant has been transferred to Create. 8 +* Create - Tenant: A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. 9 +* Deploy - Architecture: The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. 10 +* Deploy - Architecture: The machine health indicator and other progress bars have been improved visually. 11 +* Deploy - Properties: A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal. 12 +* Manage - Alerting: Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. Find out more information in our [[release blog>>Main.Release Information.Release Blogs.226 - Alerting Alchemy||target="blank"]] and our [[new alerting microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]].