Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+211 - Log Luminary

Author

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

Content

...	...	@@ -1,78 +1,84 @@
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 few weeks, we have work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that have been resolved with this release. So without further ado let us dive into all we have to offer.
	6	+**Hi there, eMagiz developers!**
6	6
7		-== **Event streaming alerting** ==
	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		-With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it.
	12	+//__Runtime logging__//
	13	+We fixed a bug where no new log messages were showing up, even though they were produced by the container.
10	10
11		-The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication that messages might be deleted before consumer groups had the option to consume the messages.
	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.
12	12
13		-The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
	18	+== **Overviews** ==
	19	+//__Runtime overview__//
	20	+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.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
	22	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
16	16
17		-The first new "dynamic" alert allows you to raise an alert once the total number of messages on one (or more topics) is less than a certain number per defined time unit. So for example you can configure an alert once the number of message placed on a topic called "Exception" is less than 15 messages within 5 minutes.
	24	+//__Missing properties overview__//
	25	+The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
	27	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
20	20
21		-The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
	29	+//__Runtime restart or redeploy overview__//
	30	+Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
22	22
23		-For more information on the generic way of working surrounding alerting please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
	32	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
24	24
25		-== **3rd generation improvements** ==
26	26
27		-//__Event Streaming statistics completion__//
28		-In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
	35	+== **Feedback Items** ==
29	29
30		-//__Deployments on next generation architecture__//
31		-This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
32	32
33		-//__Clean queues option__//
34		-This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
	38	+//__Breaking changes pop-up__//
	39	+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'.
35	35
36		-== **Feedback items ** ==
	41	+[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
37	37
38		-//__On-premise containers are started upon slot wakeup__//
39		-With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
	43	+//__External recipients emailaddress__//
	44	+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.
40	40
41		-//__Resource path is shown to the user__//
42		-You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
	46	+//__Broker queue metrics dashboards__//
	47	+It is now possible to select the MQTT broker in the queue metrics dashboards.
43	43
44		-//__Flow designer improvements__//
45		-With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
	49	+//__Runtime image version__//
	50	+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.
46	46
47		-//__Improved capabilities of a company contact__//
48		-With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
49	49
50		-== **Bug fixes ** ==
	53	+== **Bug Fixes** ==
51	51
52		-//__Optional API parameters are handled correctly__//
53		-Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
	55	+//__Message throughput__//
	56	+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.
54	54
55		-//__Without CDM rights nothing related to any data model can be edited anymore__//
56		-With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
	58	+//__Cloud template upgrade unjust rollback__//
	59	+An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
57	57
58		-//__Improved sorting of Design and Deploy archticture__//
59		-With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
	61	+//__Next generation block__//
	62	+Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
60	60
61	61	== **Fancy Forum Answers** ==
62	62
63	63	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:
64	64
65		-* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
66		-* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
67		-* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
	68	+* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
	69	+* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
	70	+* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
	71	+* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
	72	+* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
68	68
	74	+
69	69	== **Key takeaways** ==
70	70
71		-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:
	77	+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:
72	72
73	73	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74	74	* If you have feedback or ideas for us, talk to the Platypus
75		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	81	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76	76	* Clear your browser cache (Ctrl + Shift + Del)
77	77	* Check out the release notes [here]
78	78	* Start thinking about how the license tracker can aid your development
...	...	@@ -85,6 +85,12 @@
85	85	{{info}}
86	86	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
87	87
88		-~*~* Indicates a GEN3-only feature.
89		-{{/info}})))((({{toc/}}))){{/container}}
	94	+~*~* Indicates a next-generation-architecture only feature.
	95	+{{/info}}
	96	+)))
	97	+
	98	+(((
	99	+{{toc/}}
	100	+)))
90	90	{{/container}}
	102	+{{/container}}