Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+225 - TBD

Author

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

Content

...	...	@@ -1,83 +1,86 @@
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	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.
	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.
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.
	13	+[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
12	12
13		-The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
	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.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
	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.
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.
	21	+[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
18	18
19		-[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
	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]]
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.
	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.
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.WebHome||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
	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]]
24	24
25		-== **3rd generation improvements** ==
	39	+//__Unused support objects__//
	40	+Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
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.
	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.
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.
	47	+[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
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.
	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.
35	35
36		-== **Feedback items ** ==
	58	+//__Namespace update__//
	59	+Editing a namespace used in a message definition automatically updates the message definition & transformations.
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.
	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.
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.
	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.
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.
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		-
50		-== **Bug fixes ** ==
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.
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.
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.
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"]]
	71	+* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
68	68
69		-== **Key takeaways** ==
	73	+== **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:
	75	+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.
	79	+* 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		-* Check out the release notes [here]
	81	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
78	78	* Start thinking about how the license tracker can aid your development
79	79	* Start thinking about major, minor, and patch
80		-* Upgrade to the latest build number
81	81	* Keep making great integrations
82	82
83	83	Let's stay in touch and till next time!
...	...	@@ -85,6 +85,11 @@
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}}
	91	+{{/info}}
	92	+)))
	93	+
	94	+(((
	95	+{{toc/}}
	96	+)))
90	90	{{/container}}
	98	+{{/container}}