Skip to Content

Changes for page 234 - Alert Adventures

Last modified by Carlijn Kokkeler on 2024/11/18 15:29
From version 185.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
Change comment: There is no comment for this version
To version 343.1
edited by Carlijn Kokkeler
on 2024/11/18 15:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +234 - Alert Adventures
Content
... ... @@ -1,27 +1,11 @@
1 -In the last sprint cycle, we focused on ....
1 +In this release, our new error alerting will be available! Please find out more about it here (LINK). Moreover, a new runtime image is available, check it out [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]]. Lastly, we have improved the selection visibility in data models, and have fixed a bug regarding failover containers.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.234 - Alert Adventures||target="blank"]].
4 4  
5 -=====New features=====
5 +====Minor changes====
6 +* Manage - Alerting: Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, following our queue alerting design that has been [[released>>doc:Main.Release Information.Release Blogs.226 - Alerting Alchemy.WebHome||target="blank"]] several months ago. Please check out our [[release blog>>Main.Release Information.Release Blogs.234 - Alert Adventures||target="blank"]] for the migration actions, and our new microlearning (LINK) about the design.
7 +* Design - CDM: When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted. (#1150)
8 +* Deploy - Deployment: We have removed some deprecated components from our runtime image. Please find out more [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]].
6 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 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 -
11 +* Deploy - Architecture: The failover container will now be shown correctly.