Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-225 - TBD
	1	+199 - Home Improvements

Author

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

Content

...	...	@@ -1,94 +1,57 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!**
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
7	7
	7	+== **Next generation improvements and bug fixes** ==
8	8
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.
	9	+//__Enhanced overview of the HTTP Statistics__//
	10	+As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
12	12
13		-[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
	12	+//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
	13	+In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
14	14
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.
	15	+{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
17	17
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.
	17	+//__Forced congestion control__//
	18	+To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
20	20
21		-[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
	20	+//__Unused images are cleaned up__//
	21	+This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan.
22	22
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]]
	23	+== **Store Improvements** ==
27	27
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.
	25	+//__Improved importing behavior for specific use cases__//
	26	+Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
33	33
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]]
	28	+//__Fixed bug in creating a message mapping on top of an imported system message__//
	29	+It is now possbile to create a message mapping to an imported system message from the store.
38	38
39		-//__Unused support objects__//
40		-Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
	31	+== **Event Streaming - Certificate Management** ==
41	41
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.
	33	+//__Expired certification notification__//
	34	+As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
46	46
47		-[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
48		-
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.
57		-
58		-//__Namespace update__//
59		-Editing a namespace used in a message definition automatically updates the message definition & transformations.
60		-
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.
63		-
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.
66		-
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.
69		-
70		-//__Classpath conflicts__//
71		-We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
72		-
73	73	== **Fancy Forum Answers** ==
74	74
75	75	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:
76	76
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"]]
	40	+* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
	41	+* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
80	80
81		-== **Key Takeaways** ==
	43	+== **Key takeaways** ==
82	82
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:
	45	+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:
84	84
85	85	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
86	86	* If you have feedback or ideas for us, talk to the Platypus
87		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	49	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
88	88	* Clear your browser cache (Ctrl + Shift + Del)
89		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
	51	+* Check out the release notes [here]
90	90	* Start thinking about how the license tracker can aid your development
91	91	* Start thinking about major, minor, and patch
	54	+* Upgrade to the latest build number
92	92	* Keep making great integrations
93	93
94	94	Let's stay in touch and till next time!
...	...	@@ -96,11 +96,6 @@
96	96	{{info}}
97	97	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
98	98
99		-{{/info}}
100		-)))
101		-
102		-(((
103		-{{toc/}}
104		-)))
	62	+~*~* Indicates a GEN3-only feature.
	63	+{{/info}})))((({{toc/}}))){{/container}}
105	105	{{/container}}
106		-{{/container}}