Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 181.1
edited by Carlijn Kokkeler
on 2024/01/02 11:00
Change comment: There is no comment for this version
To version 179.1
edited by Carlijn Kokkeler
on 2024/01/02 10:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -12,7 +12,7 @@
12 12  * Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13 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 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. (#917)
15 +* Manage - Alerting: You can now add external recipients to your environment directly, like internal users.
16 16  * Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17 17  * Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
18 18  
... ... @@ -21,7 +21,7 @@
21 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 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 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)
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.
26 26  
27 27