Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-226 - Alerting Alchemy
	1	+200 - Uncharted Territories

Author

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

Content

...	...	@@ -1,42 +1,66 @@
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!** In this release,
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on a lot of things that are unfortanetly not quite ready to be released. As a result the ouput of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
7	7
8		-== **Feedback Items** ==
9		-//__Queue alerting__//
10		-Alerting for message queues has been improved, which includes the following improvements:
11		-* New UI that shows all queues and the alerting that is active on them.
12		-* Every queue in the model will be automatically added to the list of queues in Manage - Alerting.
13		-* Triggers of a queue will be automatically enabled or disabled based on whether that queue is included in the release.
14		-* Added 2 new trigger types "inactivity check" and "periodic activity check" that replace the "queue throughput" alert.
15		-** These checks can now run for a (very) long time, whereas the "queue throughput" was limited by 1 hour.
16		-* The alert generation has been solidified to reduce the likelihood that your alerting is affected with false positives or false negatives during eMagiz maintenance.
17		-* When the same check of multiple queues trigger at the same time, the alerts will be aggregated into a single summarized email instead of a single email per alert.
18		-
	7	+== **Next generation improvements and bug fixes** ==
	8	+
	9	+//__Enhanced right-hand view within Deployment Plan context__//
	10	+When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
	11	+
	12	+{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
	13	+
	14	+//__Improved timeout settings when deploying__//
	15	+To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
	16	+
	17	+{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	18	+
	19	+//__Detailed HTTP Statistics now show user info in specific additional cases__//
	20	+To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
	21	+
	22	+{{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}}
	23	+
	24	+//__Improved loading speed of Manage Dashboard__//
	25	+This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
	26	+
	27	+== **Store Improvements** ==
	28	+
	29	+//__Importing in Design is improved__//
	30	+We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
	31	+
19	19	== **Bug Fixes** ==
20	20
	34	+//__Deprecated reminder pop-up removed__//
	35	+We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
	36	+
	37	+//__Improved selection area in Flow Designer__//
	38	+When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow.
	39	+
	40	+//__Improved Kafka settings_//
	41	+For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
	42	+
	43	+{{info}}We stronly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
	44	+
21	21	== **Fancy Forum Answers** ==
22	22
23	23	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:
24	24
25		-* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
26		-* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
27		-* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
	49	+* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
	50	+* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
28	28
29		-== **Key Takeaways** ==
	52	+== **Key takeaways** ==
30	30
31		-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:
	54	+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:
32	32
33	33	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
34	34	* If you have feedback or ideas for us, talk to the Platypus
35		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	58	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
36	36	* Clear your browser cache (Ctrl + Shift + Del)
37		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
	60	+* Check out the release notes [here]
38	38	* Start thinking about how the license tracker can aid your development
39	39	* Start thinking about major, minor, and patch
	63	+* Upgrade to the latest build number
40	40	* Keep making great integrations
41	41
42	42	Let's stay in touch and till next time!
...	...	@@ -44,11 +44,6 @@
44	44	{{info}}
45	45	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
46	46
47		-{{/info}}
48		-)))
49		-
50		-(((
51		-{{toc/}}
52		-)))
	71	+~*~* Indicates a GEN3-only feature.
	72	+{{/info}})))((({{toc/}}))){{/container}}
53	53	{{/container}}
54		-{{/container}}