Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-194 - Giant Leap
	1	+225 - TBD

Author

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

Content

...	...	@@ -1,79 +1,94 @@
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 worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
	6	+**Hi there, eMagiz developers!**
6	6
7		-== **3rd generation improvements** ==
8	8
9		-//__Better feedback in the 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.
	9	+== **Feedback Items** ==
	10	+//__Alerting notification settings__//
	11	+The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
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 alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
	13	+[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
14	14
15		-//__Improved Manage Dashboard__//
16		-This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
	15	+//__Process containers__//
	16	+If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
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 also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. 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.
	18	+//__Design settings__//
	19	+When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
20	20
21		-//__Improved process of deploy preparation__//
22		-With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
	21	+[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
23	23
24		-//__Improved migration of Streaming container__//
25		-When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
	23	+//__Untested images__//
	24	+ A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.
	25	+
	26	+[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
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	+//__Infinispan Cache Manager__//
	29	+We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
	30	+
	31	+//__Infinispan Cache Manager error message__//
	32	+We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available.
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 help texts to clarify what each chart our table displays to you.
	34	+//__Flow bump__//
	35	+When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
	36	+
	37	+[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
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.
	39	+//__Unused support objects__//
	40	+Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
35	35
36		-{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
	42	+[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
	43	+
	44	+//__Deleting routes__//
	45	+For clarity purposes, a confirmation pop-up will be shown when deleting routes.
37	37
38		-== **Feedback items ** ==
	47	+[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
39	39
40		-//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41		-With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
	49	+//__Debug queue__//
	50	+The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
	51	+
	52	+[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
	53	+
	54	+== **Bug Fixes** ==
	55	+//__Internal server error__//
	56	+The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
42	42
43		-//__User Roles are sorted alphabetically__//
44		-All user roles under User Management are now also sorted alphabetically.
	58	+//__Namespace update__//
	59	+Editing a namespace used in a message definition automatically updates the message definition & transformations.
45	45
46		-//__Name of keystore for user management now includes the environment__//
47		-To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
	61	+//__Error pop-up__//
	62	+We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
48	48
49		-== **Bug fixes ** ==
	64	+//__SMB inbound channel adapter__//
	65	+The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new runtime image LINK is available.
50	50
51		-//__Consolidated upgrade process cloud template__//
52		-With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
	67	+//__Heap memory__//
	68	+The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available.
53	53
54		-//__Ensure users can deploy release on environments they have edit rights on__//
55		-Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
	70	+//__Classpath conflicts__//
	71	+We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
56	56
57	57	== **Fancy Forum Answers** ==
58	58
59	59	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:
60	60
61		-* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
62		-* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
63		-* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
	77	+* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
	78	+* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
	79	+* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
64	64
65		-== **Key takeaways** ==
	81	+== **Key Takeaways** ==
66	66
67		-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:
	83	+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:
68	68
69	69	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70	70	* If you have feedback or ideas for us, talk to the Platypus
71		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	87	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
72	72	* Clear your browser cache (Ctrl + Shift + Del)
73		-* Check out the release notes [here]
	89	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
74	74	* Start thinking about how the license tracker can aid your development
75	75	* Start thinking about major, minor, and patch
76		-* Upgrade to the latest build number
77	77	* Keep making great integrations
78	78
79	79	Let's stay in touch and till next time!
...	...	@@ -81,6 +81,11 @@
81	81	{{info}}
82	82	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83	83
84		-~*~* Indicates a GEN3-only feature.
85		-{{/info}})))((({{toc/}}))){{/container}}
	99	+{{/info}}
	100	+)))
	101	+
	102	+(((
	103	+{{toc/}}
	104	+)))
86	86	{{/container}}
	106	+{{/container}}