Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 59.1
edited by Erik Bakker
on 2023/03/14 08:51
Change comment: There is no comment for this version
To version 178.1
edited by Carlijn Kokkeler
on 2023/12/22 12:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Giant Leap
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,33 +1,27 @@
1 -The release introduces various improvements on our 3rd generation runtime architecture and various other fixes in other parts of the portal. Subsequently, we will release a new runtime image supporting the various improvements.
1 +In the last sprint cycle, we focused on improving several aspects related to 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.194 - Giant Leap.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 5  =====New features=====
6 6  
7 -* A new runtime image for customer models running on the 3rd generation runtime. Please learn more about our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V131.WebHome||target="blank"]].
8 -* Deploy - Architecture: Putting your cloud slot to sleep will stop your local docker containers and waking up a cloud slot will start those containers. (#889)
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 in an overview.
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.
9 9  
10 10  =====Minor changes=====
11 11  
12 -* Create - 3rd generation runtime migration: When migrating your event streaming container to the 3rd generation runtime, the event streaming infra flow will be updated correctly based on whether you are using custom error handling on your event processors or not.
13 -* Deploy - User Management: Consistent naming download buttons and filename certificate contains environment (#807)
14 -* Deploy - User Management: Roles are sorted alphabetically. (#806)
15 -* Deploy - Architecture: We removed the deprecated cloud update feature from the ‘Details' popup. Please use the ‘Upgrade’ feature to keep your cloud architecture up-to-date.
16 -* Manage - Event Streaming Statistics: Updated graphs to display the average of the selected timeframe, added help texts to each table and graph and made some small visual improvements.
17 -* Manage - Alerting: History is recorded when notifications are paused or unpaused. (#833)
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: Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
15 +* Manage - Alerting: You can now add external recipients to your environment directly, like internal users.
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 18  
19 19  ====Bug fixes====
20 20  
21 -* Generic: We fixed an issue that you may see a screen with a broken styling when switching among phases.
22 -* Create - Flow Designer: Removed the option to create a new resource on resource selection pop-up of simple XSD schema support object.
23 -* Create - Flow designer: We fixed the flow generation of entry flows for API Key secured API Gateway operations. This problem was introduced in version 193 (2023-02-04). (#902)
24 -* Create - Resources: We fixed an issue when deploying flows with uploaded resources with very long filename (>100 characters).
25 -* Deploy - Releases: You need edit rights in test environment of deploy phase to execute “Update flows to latest versions” action.
26 -* Manage - Dashboard: We update the view to visualize the split entries after you do a migration a combined entries.
27 -* Manage - Logging: When a container cannot be started due to an incorrect stylesheet, the error message will include what the error is and in which stylesheet is occurred (#825)
28 -* Manage - Logging: Reduced the occurance of 'Failed to send to Elastic' log messages which triggers alerts. (#898)
29 -* Manage - Alerting: Editable column shows the correct value.
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 unjustly 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 the container.
25 +* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal.
30 30  
31 -====Remarks====
32 32  
33 -* Create - Flow designer: After the deployment, the ‘Version Compare' and 'Version Restore’ features will be unavailable for a few hours, because of data migration. You will get an error stating that the version is not compatible with the selected feature until migration has finished.