Changes for page 234 - Alert Adventures
Last modified by Carlijn Kokkeler on 2024/11/18 15:29
From version 171.1
edited by Carlijn Kokkeler
on 2023/12/21 16:02
on 2023/12/21 16:02
Change comment:
There is no comment for this version
To version 323.1
edited by Carlijn Kokkeler
on 2024/09/23 13:48
on 2024/09/23 13:48
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 11-Log Luminary1 +230 - Petite Peaks - Content
-
... ... @@ -1,24 +1,10 @@ 1 - Inthelast sprint cycle, wefocused onimproving severalaspects relatedoverviewsandlogging.It isnowpossibleto see an overview ofall runtimesonrunningmachines,see runtimesandflowversionsin themissingpropertiesoverview,andsee whichruntimes willberestarted orredeployedina pop-updisplayed whenstarting thedeploymentplan. Moreover,crash handlinghas beenimproved,aswell asruntimelogging and thedisplay ofthedeployment executionerrormessage.Lastly, severaltherminorchangesand bug fixeshavebeendone,mainly relatingtotheDeploy and Manage phase.1 +During our recent sprint cycle, we improved the functionality of adding an integration to an existing API in Design, ensured that queues with illegal characters will not generate errors anymore, and we fixed an issue where the execution of a deployment step would be blocked. Read all about it below! 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 11-Log Luminary||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.230 - Petite Peaks||target="blank"]]. 4 4 5 -=====New features===== 5 +====Minor changes==== 6 +* Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited. 6 6 7 -* Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots of the release in the Deploy phase. 8 - 9 -=====Minor changes===== 10 - 11 -* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 12 -* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images. 13 - 14 14 ====Bug fixes==== 15 - 16 -* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 17 -* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. (#1100) 18 -* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 19 -* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck. 20 -* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 21 -* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives. 22 -* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 23 - 24 - 9 +* Manage - Explore: Queues with illegal characters will not generate errors anymore. 10 +* Deploy - Deployment: We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.