197 - Pay Attention

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.

Please find out more on our Release blog.

New features

• Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template release notes for more information.
• 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 for additional information.

Minor changes

• Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
• 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."
• Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.

Bug fixes

• 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.
• Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952)
• Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947)
• Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
• 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. Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments.
• Design - Message Definitions: "Message format" button is also available in view mode. (#919)

Remarks

• 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.