Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23

From version 328.1
edited by Carlijn Kokkeler
on 2024/10/07 15:08
Change comment: There is no comment for this version
To version 185.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -231 - Microscopic Madness
1 +212 - Failover Fiesta
Content
... ... @@ -1,18 +1,27 @@
1 -During our recent sprint cycle, we have improved the search options for flow testing logs and monitoring logs. Next to this, we fixed the unused properties overview and improved the deletion functionality of router containers.
1 +In the last sprint cycle, we focused on ....
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.231 - Microscopic Madness||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
5 +=====New features=====
5 5  
6 -====Minor changes====
7 -* Create - Flow Testing: Search options for flow testing logs have been improved.
8 -** Improved search options for flow test logs. You can now search for 'logger' and 'message', search for 'timestamp from' and 'to' have been removed.
9 -** Unified the UI with Manage phase logging of G3) for a more streamlined experience
10 -* Manage - Monitoring: Search options for monitoring logs have been improved.
11 -** Unified the UI with flow testing log interface, showing the message and stack trace (if available) in 2 different tabs
12 -** Added the 'logger' column that shows the last part of the logger name.
13 -** Added a search field for ‘logger’
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.
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.
14 14  
10 +=====Minor changes=====
15 15  
12 +* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13 +* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
14 +* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
15 +* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
16 +* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
18 +
16 16  ====Bug fixes====
17 -* Deploy - Architecture: Router containers that were deleted from the Deploy Architecture, are now cleaned up completely from the environment.
18 -* Deploy - Releases: We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. (#1442)
20 +
21 +* 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.
22 +* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
23 +* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24 +* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
25 +* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
26 +
27 +