Changes for page 232 - Bug Busters
Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 283.1
edited by Carlijn Kokkeler
on 2024/07/29 14:00
on 2024/07/29 14:00
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 (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 26-AlertingAlchemy1 +211 - Log Luminary - Content
-
... ... @@ -1,12 +1,24 @@ 1 - Duringour recent sprint cycle, wehave workedto release anew designforqueue alerting.Moreover,we have worked ontenantitems, machine pop-ups and progressbars,and theInfinispanCacheManager.Pleasefindoutallbelow!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 26-AlertingAlchemy||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]]. 4 4 5 -====Minor changes==== 6 -* Create - Flow Designer: The Infinispan Cache Manager has been updated to provide an additional 'transport type' to offer more means for creating a clustered setup, provide clearer helptexts, and include validation on fields depending on the selected 'transport type'. 7 -* Design - Tenant: The technical name of a tenant cannot be changed once the tenant has been transferred to Create. 8 -* Create - Tenant: A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. 9 -* Deploy - Architecture: The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. 10 -* Deploy - Architecture: The machine health indicator and other progress bars have been improved visually. 11 -* Deploy - Properties: A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal. 12 -* Manage - Alerting: Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. Find out more information in our [[release blog>>Main.Release Information.Release Blogs.226 - Alerting Alchemy||target="blank"]] and our [[new alerting microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]]. 5 +=====New features===== 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 +====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 +