Wiki source code of 197 - Pay Attention
Version 77.1 by Erik Bakker on 2023/05/09 13:55
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
77.1 | 1 | Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments. |
![]() |
1.1 | 2 | |
![]() |
77.1 | 3 | Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]]. |
![]() |
35.1 | 4 | |
![]() |
66.1 | 5 | =====New features===== |
![]() |
77.1 | 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. | ||
![]() |
66.1 | 8 | |
![]() |
46.1 | 9 | =====Minor changes===== |
![]() |
37.1 | 10 | |
![]() |
77.1 | 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. | ||
![]() |
37.1 | 14 | |
![]() |
24.1 | 15 | ====Bug fixes==== |
![]() |
17.1 | 16 | |
![]() |
77.1 | 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: You can apply your changes to only one or both zones on 3rd generation double-lane models. | ||
19 | * Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture. | ||
20 | * 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. | ||
21 | * Design - Message Definitions: "Message format" button is also available in view mode. (#919) |