Changes for page 247.1 - Help Out
Last modified by Erik Bakker on 2025/06/25 19:51
From version 265.1
edited by Erik Bakker
on 2025/06/17 09:12
on 2025/06/17 09:12
Change comment:
There is no comment for this version
To version 172.1
edited by Carlijn Kokkeler
on 2023/12/21 16:06
on 2023/12/21 16:06
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 -2 47-HelpOut1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,12 +1,24 @@ 1 - This release focusesonhelpingour communitybyimprovingvariousaspects ofourplatforminanticipationofsomeofthe largerfeatures that arejustaroundthecorner.So, withoutfurtherado,let'stake a lookatwhat'sonthe menutoday!1 +In the last sprint cycle, we focused on improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 47-HelpOut.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]]. 4 4 5 -==== Bugfixes5 +=====New features===== 6 6 7 -* Design - Architecture: A change is made to ensure that the "Design architecture" is correctly updated based on message type changes in the Capture phase. (#1614) 8 -* Design - System: New help text is generated for the “SOAP entry connector” check box. The check box is present in the "Design phase" while editing the system. (#1413) 9 -* Create - Flow designer: On the "File item reader message source," various help texts have been added to give additional clarity on what the component does. (#1463) 10 -* Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow is corrected so that the flow is deployed with the correct flow version and component list. (#1618) 11 -* Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture. It shows the topic retention bytes, as users are only allowed to modify this variable. (#1358) 12 -* Manage - Explore: The bug is fixed so that all the options within the explore section of the Manage phase are responsive at all times. (#1524) 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 +====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 +