Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 174.1
edited by Carlijn Kokkeler
on 2023/12/21 16:18
on 2023/12/21 16:18
Change comment:
There is no comment for this version
To version 77.1
edited by Erik Bakker
on 2023/05/09 13:55
on 2023/05/09 13:55
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 - 211-LogLuminary1 +197 - Pay Attention - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,31 +1,21 @@ 1 - Inlast sprintcycle, we focusedonimproving several aspectsrelated overviewsandlogging.It isnow possibletoseeanoverviewof allruntimesonrunning machines,seeuntimesandflow versionsin themissing propertiesoverview, andsee whichruntimes will berestartedorredeployed inapop-up displayedwhen startingthe deploymentplan.Moreover,crashhandlinghasbeenimproved, as well as runtimeloggingand the displayofthedeployment execution errormessage.Lastly,severalother minor changes and bug fixeshave beendone,mainlyrelatingto theDeploy and Managephase.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. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 211-LogLuminary||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]]. 4 4 5 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. 6 6 7 -* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview. 8 -* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 9 - 10 - 11 - 12 - 13 - 14 14 =====Minor changes===== 15 15 16 -* Deploy-Deployment:The missingproperties overview hasbeenupdatedtoshow theruntimes andflowversionsof missingpropertyvalues.17 -* Deploy - Architecture:Pendingchanges that have ahighrisklevelarenowshowninredbold inthepopupthatappearsafterclicking'Apply toenvironment'.18 -* Manage -Monitoring: We improvedcrash handlingsothatlogmessagesclearlyshow whenand whyacontainerfailedtostart.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. 19 19 20 - 21 - 22 - 23 - 24 24 ====Bug fixes==== 25 25 26 -* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. 27 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container. 28 - 29 - 30 - 31 - 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)