Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-210 - Deployment Delights
	1	+211 - Log Luminary

Content

...	...	@@ -3,49 +3,62 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
	6	+**Hi there, eMagiz developers!**
7	7
8		-== **Alerts** ==
	8	+== **Overviews and logging** ==
	9	+//__Runtime overview__//
	10	+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.
9	9
10		-//__Topic approaching max size alert__//
11		-The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
	12	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
12	12
13		-//__Missing metrics alert__//
14		-We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
	14	+//__Missing properties overview__//
	15	+The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
15	15
	17	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
	18	+
	19	+//__Runtime restart or redeploy overview__//
	20	+Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
	21	+
	22	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
	23	+
	24	+//__Missing log entries__//
	25	+We improved crash handling so that log messages clearly show when and why a container failed to start.
	26	+
	27	+//__Runtime logging__//
	28	+We fixed a bug where no new log messages were showing up, even though they were produced by the container.
	29	+
16	16	== **Feedback Items** ==
17	17
18		-//__Improved release build process__//
19		-When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
20	20
21		-//__Container version overview__//
22		-Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
	33	+//__Breaking changes pop-up__//
	34	+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'.
23	23
24		-[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
	36	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
25	25
26		-//__Improved deployment process__//
27		-The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
	38	+//__External recipients emailaddress__//
	39	+The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
28	28
29		-//__Rebuilding of images__//
30		-Changing the list of flows that should run on a container will now trigger the rebuilding of images.
	41	+//__Broker queue metrics dashboards__//
	42	+It is now possible to select the MQTT broker in the queue metrics dashboards.
31	31
32		-== **Bug Fixes** ==
	44	+//__Runtime image version__//
	45	+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.
33	33
34		-//__Runtime metrics processing__//
35		-The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
36	36
37		-//__Deployment plan__//
38		-We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
	48	+== **Bug Fixes** ==
39	39
40		-//__View all store items__//
41		-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.
	50	+//__Message throughput__//
	51	+The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
42	42
43		-//__Out of memory behavior__//
44		-We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
	53	+//__Cloud template upgrade unjust rollback__//
	54	+An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
45	45
46		-//__Max fetch size__//
47		-In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
	56	+//__Next generation block__//
	57	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
48	48
	59	+//__Deployment execution error message__//
	60	+In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
	61	+
49	49	== **Fancy Forum Answers** ==
50	50
51	51	As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: