Changes for page 232 - Bug Busters
Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 80.1
edited by Erik Bakker
on 2023/05/12 09:14
on 2023/05/12 09:14
Change comment:
There is no comment for this version
To version 281.1
edited by Carlijn Kokkeler
on 2024/07/29 13:58
on 2024/07/29 13:58
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 197-PayAttention1 +226 - Alerting Alchemy - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,26 +1,13 @@ 1 - Another couple of weeks have passed, so it is time fora new release. We have delivered additionalminor (bug) fixes in thisreleaseandreleased the event streamingalerting.Thelast is a real improvementin managing yourventstreaming solution.Furthermore, you will find several enhancementsin working in nextGenenvironments.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. 197-PayAttention.WebHome||target=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 -* 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. 7 -* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information. 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. 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"]]. 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 - 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. 10 +* Deploy - Architecture: The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. 11 +* Deploy - Architecture: The machine health indicator and other progress bars have been improved visually. 12 +* 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'. 8 8 9 -=====Minor changes===== 10 - 11 -* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated. 12 -* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute." 13 -* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments. 14 - 15 -====Bug fixes==== 16 - 17 -* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item. 18 -* Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952) 19 -* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947) 20 -* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture. 21 -* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. 22 -* Design - Message Definitions: "Message format" button is also available in view mode. (#919) 23 - 24 -====Remarks==== 25 - 26 -* Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture. Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off.