Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 102.1
edited by Erik Bakker
on 2023/08/15 12:23
on 2023/08/15 12:23
Change comment:
There is no comment for this version
To version 173.1
edited by Carlijn Kokkeler
on 2023/12/21 16:12
on 2023/12/21 16:12
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 03-FastPaced1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,19 +1,19 @@ 1 -In the last sprint cycle, we focused on the scalabilityandstabilityofour infrastructure.Ontopofthat, we will release severalinor changes with apotentially significantimpact.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 03-Fast Paced.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]]. 4 4 5 +=====New features===== 6 + 7 + 8 + 5 5 =====Minor changes===== 6 6 7 -* Create - Integrations: Improved the performance of adding or removing API gateway integrations for split entry configurations. (#1023) 8 -* Manage - Alerting: Identifiers of triggers are now visible in the edit screen. 11 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start. 9 9 13 + 14 + 10 10 ====Bug fixes==== 11 11 12 -* Create - Flows: Fixed an issue where removing some split entry flows from Create phase was not possible after splitting your all entry/combined entry flow. (#1016) 13 -* Deploy - Releases: We fixed an issue that your release contains a JMS server flow twice with different build version numbers when adding another flow to your release. (#597) 14 -* Deploy properties: When a user activates a release containing nested properties and the property is not created, we show it now as missing. On top of that, we add the property placeholder after the user tries to activate the release. 15 15 16 -=====Infra and image changes===== 17 17 18 -* Infrastructure: Tightened security policies for a more secure infrastructure. 19 -* Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower 19 +