Skip to Content

Changes for page 234 - Alert Adventures

Last modified by Carlijn Kokkeler on 2024/11/18 15:29
From version 343.1
edited by Carlijn Kokkeler
on 2024/11/18 15:23
Change comment: There is no comment for this version
To version 88.1
edited by Erik Bakker
on 2023/06/06 08:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -234 - Alert Adventures
1 +199 - Home Improvements
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,11 +1,20 @@
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.
1 +In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, the store, security, and certificate management.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.234 - Alert Adventures||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]].
4 4  
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"]].
5 +=====Minor changes=====
9 9  
7 +* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store.
8 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 +* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899)
10 +* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately three months before event streaming users' access certificates expire.
11 +* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan.
12 +* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960)
13 +* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.
14 +* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.
15 +
10 10  ====Bug fixes====
11 -* Deploy - Architecture: The failover container will now be shown correctly.
17 +
18 +* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864)
19 +* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937)
20 +