Skip to Content

Changes for page 234 - Alert Adventures

Last modified by Carlijn Kokkeler on 2024/11/18 15:29
From version 172.1
edited by Carlijn Kokkeler
on 2023/12/21 16:06
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 -211 - Log Luminary
1 +234 - Alert Adventures
Content
... ... @@ -1,24 +1,11 @@
1 -In the last sprint cycle, we focused on improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.
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.211 - Log Luminary||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 - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots of the release in the Deploy phase.
8 -
9 -=====Minor changes=====
10 -
11 -* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
12 -* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images.
13 -
14 14  ====Bug fixes====
15 -
16 -* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
17 -* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. (#1100)
18 -* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
19 -* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
20 -* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
21 -* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
22 -* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
23 -
24 -
11 +* Deploy - Architecture: The failover container will now be shown correctly.