Changes for page 240 - Spring Cleaning

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,27 +1,24 @@
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.
	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	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		-* 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.
	7	+* Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots of the release in the Deploy phase.
9	9
10	10	=====Minor changes=====
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.
	11	+* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
	12	+* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images.
18	18
19	19	====Bug fixes====
20	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.
	16	+* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
	17	+* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. (#1100)
	18	+* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
	19	+* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
	20	+* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
	21	+* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
	22	+* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
26	26
27	27