Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-199 - Home Improvements
	1	+224 - Summer Sonata

Author

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

Content

...	...	@@ -1,58 +1,63 @@
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 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.
	6	+**Hi there, eMagiz developers!** Over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor.
6	6
7		-== **Next generation improvements and bug fixes** ==
	8	+== **Feedback Items** ==
	9	+//__Retention duration and bytes requirements__//
	10	+The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes.
8	8
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	+//__Used message types__//
	13	+It is now possible to filter the message types in Capture on whether they are used.
11	11
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.
	15	+[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]]
	16	+
	17	+//__Debugger duration__//
	18	+Wiretaps and debugging sessions will now collect messages for ten minutes, this used to be five. Note that the JMS server needs to be updated in order to also store the messages for ten minutes instead of five. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
14	14
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}}
	20	+== **Bug Fixes** ==
	21	+//__SFTP sessions__//
	22	+Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
16	16
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.
	24	+[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
19	19
20	20
21		-//__Improved validation errors on the invalid configuration of HTTP outbound components__//
22		-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.
	27	+[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
23	23
24		-//__Improved migration behavior__//
25		-This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
26		-A smoother migration of your JMS (and backup JMS) process.
27		-Shortening of names that otherwise would be too long, additional feedback given to the user.
28		-Feedback when the migration process is finished.
	29	+//__SMB outbound gateway__//
	30	+The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
29	29
30		-//__Additional checks when deploying__//
31		-This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
	32	+//__TaskScheduler__//
	33	+In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
32	32
33		-== **Store Improvements** ==
	35	+//__View XSLT__//
	36	+We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
34	34
35		-== **Event Streaming - Certificate Management** ==
	38	+//__Multipart/form-data HTTP request__//
	39	+The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available.
36	36
37	37	== **Fancy Forum Answers** ==
38	38
39	39	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:
40	40
41		-* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
42		-* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
	45	+* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
	46	+* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
	47	+* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
	48	+* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
43	43
44		-== **Key takeaways** ==
	50	+== **Key Takeaways** ==
45	45
46		-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:
	52	+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:
47	47
48	48	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
49	49	* If you have feedback or ideas for us, talk to the Platypus
50		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	56	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
51	51	* Clear your browser cache (Ctrl + Shift + Del)
52		-* Check out the release notes [here]
	58	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
53	53	* Start thinking about how the license tracker can aid your development
54	54	* Start thinking about major, minor, and patch
55		-* Upgrade to the latest build number
56	56	* Keep making great integrations
57	57
58	58	Let's stay in touch and till next time!
...	...	@@ -60,6 +60,11 @@
60	60	{{info}}
61	61	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
62	62
63		-~*~* Indicates a GEN3-only feature.
64		-{{/info}})))((({{toc/}}))){{/container}}
	68	+{{/info}}
	69	+)))
	70	+
	71	+(((
	72	+{{toc/}}
	73	+)))
65	65	{{/container}}
	75	+{{/container}}