Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-194 - Big Leap
	1	+211 - Log Luminary

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,87 +1,78 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
	6	+**Hi there, eMagiz developers!** In this release, we have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes, mainly relating to the Deploy and Manage phase.
6	6
7		-== **3rd generation improvements** ==
	8	+== **Logging** ==
	9	+//__Missing log entries__//
	10	+We improved crash handling so that log messages clearly show when and why a container failed to start.
8	8
9		-//__Better feedback in error log when a corrupt stylesheet is encountered__//
10		-We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
	12	+//__Runtime logging__//
	13	+We fixed a bug where no new log messages were showing up, even though they were produced by the container.
11	11
12		-//__Better internal error handling to avoid unnecessary alerting and notifications__//
13		-We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
	15	+//__Deployment execution error message__//
	16	+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.
14	14
15		-//__Improved Manage Dashboard__//
16		-This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
	18	+== **Overviews** ==
17	17
18		-//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19		-When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
	20	+//__Runtime overview__//
	21	+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.
20	20
21		-//__Improved process of deploy preparation__//
22		-With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
	23	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
23	23
24		-//__Improved migration of Streaming container__//
25		-When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
	25	+//__Missing properties overview__//
	26	+The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
26	26
27		-//__Add History to Notifications in Manage__//
28		-To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
	28	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
29	29
30		-//__Improved Manage phase for Event Streaming__//
31		-Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
	30	+//__Runtime restart or redeploy overview__//
	31	+Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
32	32
33		-//__Improved help text for network volumes__//
34		-With this release we have improved the help text that explains network volumes and how to use them within our solution.
	33	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
35	35
	35	+== **Feedback Items** ==
36	36
	37	+//__Breaking changes pop-up__//
	38	+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'.
37	37
38		-{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3.WebHome||target="blank"]] on the subject.{{/warning}}
	40	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
39	39
40		-== **WS-Security on the 3rd generation runtime** ~*~* ==
	42	+//__External recipients emailaddress__//
	43	+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.
41	41
42		-To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols. Please make sure to create a new release that will trigger the image creation process which will included this feature when necessary.
	45	+//__Broker queue metrics dashboards__//
	46	+It is now possible to select the MQTT broker in the queue metrics dashboards.
43	43
44		-== **State Generation ~*~* ==
	48	+//__Runtime image version__//
	49	+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.
45	45
46		-With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community.
47	47
48		-{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}}
	52	+== **Bug Fixes** ==
49	49
50		-== **Feedback items ** ==
	54	+//__Message throughput__//
	55	+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.
51	51
52		-//__Removed OData as option for an API Gateway operation__//
53		-With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
	57	+//__Cloud template upgrade unjust rollback__//
	58	+An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
54	54
55		-//__Changes in API Gateway operation paths is automatically updated in Create__//
56		-When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
	60	+//__Next generation block__//
	61	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
57	57
58		-{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
59		-
60		-== **Bug fixes ** ==
61		-
62		-//__Prevent endless loop in Deploy -> User Management__//
63		-With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
64		-
65		-{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
66		-
67		-//__Update error handling during migration to the 3rd generation runtime__//
68		-As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
69		-
70	70	== **Fancy Forum Answers** ==
71	71
72	72	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:
73	73
74		-* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
75		-* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
76		-* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
	67	+* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
77	77
78	78	== **Key takeaways** ==
79	79
80		-Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	71	+Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
81	81
82	82	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83	83	* If you have feedback or ideas for us, talk to the Platypus
84		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	75	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
85	85	* Clear your browser cache (Ctrl + Shift + Del)
86	86	* Check out the release notes [here]
87	87	* Start thinking about how the license tracker can aid your development
...	...	@@ -94,6 +94,12 @@
94	94	{{info}}
95	95	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
96	96
97		-~*~* Indicates a GEN3-only feature.
98		-{{/info}})))((({{toc/}}))){{/container}}
	88	+~*~* Indicates a next-generation-architecture only feature.
	89	+{{/info}}
	90	+)))
	91	+
	92	+(((
	93	+{{toc/}}
	94	+)))
99	99	{{/container}}
	96	+{{/container}}