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	+226 - Alerting Alchemy

Author

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

Content

...	...	@@ -1,59 +1,68 @@
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!** In this release,
6	6
7		-== **Next generation improvements and bug fixes** ==
	8	+== **Feedback Items** ==
	9	+//__Queue alerting__//
	10	+Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, 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.
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.
	19	+If your model is running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, you will be migrated on the day of release. eMagiz will transfer the queue alerts that you have currently configured to the closest match in the new alerting stack. Models that are in the process of migrating to the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture during the time of the release of this feature will be able to pre-configure their new queue alert triggers, but will not be able to make active use of them until the runtime migration has finished.
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.
	21	+{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
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}}
	23	+[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
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.
	25	+//__Tenant technical name__//
	26	+ The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
19	19
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.
	28	+//__Tenant transfer__//
	29	+A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
22	22
23		-//__Improved rollup and storage of metrics when running an event streaming solution__//
24		-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.
	31	+//__Property placeholder__//
	32	+A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
25	25
26		-{{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 July. From then on, all data before the 9th of June 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}}
	34	+//__Machine pop-up__//
	35	+* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
	36	+* The machine health indicator has been improved visually.
	37	+* Several progress bars have been improved visually.
27	27
28		-== **Store Improvements** ==
	39	+[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]]
	40	+
	41	+//__Infinispan Cache Manager__//
	42	+The Infinispan Cache Manager has been updated to:
	43	+* Provide an additional 'transport type' to offer more means for creating a clustered setup;
	44	+* Provide clearer helptexts explaining which of the options is needed and what its effect is;
	45	+* Include validation on fields depending on the selected 'transport type'.
29	29
30		-//__Improved importing behavior for specific use cases__//
31		-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.
32		-
33		-== **Event Streaming - Certificate Management** ==
34		-
35		-//__Expired certification notification__//
36		-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]].
37		-
38	38	== **Fancy Forum Answers** ==
39	39
40	40	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:
41	41
42		-* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
43		-* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
	51	+* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
	52	+* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
	53	+* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
44	44
45		-== **Key takeaways** ==
	55	+== **Key Takeaways** ==
46	46
47		-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:
	57	+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:
48	48
49	49	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
50	50	* If you have feedback or ideas for us, talk to the Platypus
51		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	61	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
52	52	* Clear your browser cache (Ctrl + Shift + Del)
53		-* Check out the release notes [here]
	63	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
54	54	* Start thinking about how the license tracker can aid your development
55	55	* Start thinking about major, minor, and patch
56		-* Upgrade to the latest build number
57	57	* Keep making great integrations
58	58
59	59	Let's stay in touch and till next time!
...	...	@@ -61,6 +61,11 @@
61	61	{{info}}
62	62	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63	63
64		-~*~* Indicates a GEN3-only feature.
65		-{{/info}})))((({{toc/}}))){{/container}}
	73	+{{/info}}
	74	+)))
	75	+
	76	+(((
	77	+{{toc/}}
	78	+)))
66	66	{{/container}}
	80	+{{/container}}