Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+225 - Pop-up Party

Content

...	...	@@ -1,73 +1,90 @@
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 hard on improving our next-generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore, several smaller feedback items and bugs have been resolved with this release. So without further ado, let us dive into all we have to offer.
	6	+**Hi there, eMagiz developers!** In this release, a new runtime image (LINK) will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below!
6	6
7		-== **Event streaming alerting** ==
	8	+== **Feedback Items** ==
	9	+//__Alerting notification settings__//
8	8
9		-This release expands our alerting functionality into the event streaming pattern. As of now, one new "static" alert has been introduced for all clients (using event streaming), and two "dynamic" alerts have been introduced that you can configure yourself if there is a need for it.
	11	+//__Process containers__//
	12	+If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern.
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 into whether messages on it are deleted due to a size or time constraint. In cases where data is deleted, the topic was too full way before the messages should have been removed due to the retention hours constraint. This alert can indicate that messages might be deleted before consumer groups had the option to consume the messages.
	14	+//__Design settings__//
	15	+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.
12	12
13		-The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
	17	+[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
14	14
15		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
	19	+//__Untested images__//
	20	+ 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.
	21	+
	22	+[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
16	16
17		-The first new "dynamic" alert allows you to raise an alert once the 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 messages placed on a topic called "Exception" is less than 15 messages within 5 minutes.
	24	+//__Infinispan Cache Manager__//
	25	+We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
	26	+
	27	+//__Infinispan Cache Manager error message__//
	28	+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.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
	30	+//__Flow bump__//
	31	+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.
	32	+
	33	+[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
20	20
21		-The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups are more than X messages behind on one or more topics. The configuration of this is comparable to what we saw before.
	35	+//__Unused support objects__//
	36	+Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
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"]].
	38	+[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
	39	+
	40	+//__Deleting routes__//
	41	+For clarity purposes, a confirmation pop-up will be shown when deleting routes.
24	24
25		-== **3rd generation improvements** ==
	43	+[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
26	26
27		-//__Increased grace period for shutdown__//
28		-In this release, we have increased a container's grace period to shut down before it is forcefully shut down. This should reduce the chance of unwanted failover behavior within your model.
	45	+//__Debug queue__//
	46	+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.
	47	+
	48	+[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
	49	+
	50	+== **Bug Fixes** ==
	51	+//__Internal server error__//
	52	+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.
29	29
30		-//__Update at once or not__//
31		-This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
	54	+//__Namespace update__//
	55	+Editing a namespace used in a message definition automatically updates the message definition & transformations.
32	32
33		-//__Improved user feedback while executing a deployment plan__//
34		-This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information about why this cannot be executed is shown to the user. This way, they can take this information and act upon it instead of assuming everything went well.
	57	+//__Error pop-up__//
	58	+We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
35	35
36		-//__Improved auto-healing when running in a hybrid situation__//
37		-In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
	60	+//__SMB inbound channel adapter__//
	61	+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.
38	38
39		-//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
40		-To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
	63	+//__Heap memory__//
	64	+The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available.
41	41
42		-{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
	66	+//__Classpath conflicts__//
	67	+We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
43	43
44		-== **Feedback items ** ==
45		-
46		-//__Make sure the message format can be viewed without "Start editing"__//
47		-With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
48		-
49		-//__Various styling improvements in the flow testing functionality__//
50		-Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
51		-
52	52	== **Fancy Forum Answers** ==
53	53
54	54	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:
55	55
56		-* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
57		-* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
	73	+* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
	74	+* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
	75	+* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
58	58
59		-== **Key takeaways** ==
	77	+== **Key Takeaways** ==
60	60
61		-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:
	79	+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:
62	62
63	63	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64	64	* If you have feedback or ideas for us, talk to the Platypus
65		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	83	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66	66	* Clear your browser cache (Ctrl + Shift + Del)
67		-* Check out the release notes [here]
	85	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
68	68	* Start thinking about how the license tracker can aid your development
69	69	* Start thinking about major, minor, and patch
70		-* Upgrade to the latest build number
71	71	* Keep making great integrations
72	72
73	73	Let's stay in touch and till next time!
...	...	@@ -75,6 +75,11 @@
75	75	{{info}}
76	76	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77	77
78		-~*~* Indicates a GEN3-only feature.
79		-{{/info}})))((({{toc/}}))){{/container}}
	95	+{{/info}}
	96	+)))
	97	+
	98	+(((
	99	+{{toc/}}
	100	+)))
80	80	{{/container}}
	102	+{{/container}}