Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 177.1
edited by Carlijn Kokkeler
on 2023/12/21 16:28
Change comment: There is no comment for this version
To version 1.2
edited by eMagiz
on 2022/10/14 13:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +185 - Get Ready
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.eMagiz
Content
... ... @@ -1,27 +1,18 @@
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.
1 +Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.184 - New Beginnings.WebHome||target="blank"]].
4 4  
5 5  =====New features=====
6 +* Create - new flow designer has been introduced for all users in the Create phase
7 + ** Right hand panel that displays alerts, properties, support objects and resources
8 + ** Objects can now be put on the canvas without a full configuration
9 + ** Alerts are generated to display incorrect or incomplete configuration
10 + ** Flow versions can be pushed to Deploy only when there are no remaining alerts
6 6  
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=====
14 +* Deploy - Copy property page changed to have a orientation on the runtime. Includes update to that popup for the field runtime
11 11  
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 -
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.
26 -
27 -
18 +* Feedback widget - introduced new version and fixed the interaction