Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+226 - Alerting Alchemy

Content

...	...	@@ -1,64 +1,59 @@
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 done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
	6	+**Hi there, eMagiz developers!** The past few weeks we have worked hard to release our new queue alerting design. Please find out all new features in our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning. Note that the new queue alerting will not yet be availalbe for queues with message redelivery. Next to alerting, we have worked on tenant items, machine pop-ups and progress bars, and the Infinispan Cache Manager. Find out all below!
6	6
7		-== **Deployment Plan** ==
8		-
9		-//__Improved deployment plan to make the process better and more predictable__//
10		-The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
11		-
12		-//__Editing release properties__//
13		-With this release, it will be possible to change the description of a property by editing the property.
14		-
15		-//__JMS memory setting check__//
16		-A change in memory settings triggers redeployment of the container now.
17		-
18		-//__Properties tab__//
19		-We have removed the deprecated tab Properties in the Deploy phase.
20		-
21		-//__Cleanup old images__//
22		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
23		-
24		-== **Store Improvements** ==
25		-
26		-
27	27	== **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.
28	28
29		-//__Alerting manual pause__//
30		-A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
	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.
31	31
32		-//__Ordering of graphs in Manage__//
33		-The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
	21	+{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
34	34
35		-//__UTC times in Grafana panels__//
36		-All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
	23	+{{info}}Please check out our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning for an elaborate explanation of our new queue alerting design. {{/info}}
37	37
38		-//__Update flow designer version__//
39		-The framework used in the flow designer has been updated to the latest version.
	25	+[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
40	40
41		-//__Carwash track TLS versions in logging__//
42		-A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
	27	+//__Tenant technical name__//
	28	+ The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
43	43
44		-//__Moving channels in the flow designer__//
45		-Moving already attached channels in the flow designer has been made sligthly easier.
	30	+//__Tenant transfer__//
	31	+A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
46	46
47		-//__Topic sizes description change__//
48		-In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
	33	+//__Property placeholder__//
	34	+A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
49	49
50		-//__Topic sizes description change__//
	36	+//__Machine pop-up__//
	37	+* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
	38	+* The machine health indicator has been improved visually.
	39	+* Several progress bars have been improved visually.
	40	+
	41	+[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]]
51	51
52		-== **Bug Fixes** ==
	43	+//__Infinispan Cache Manager__//
	44	+The Infinispan Cache Manager has been updated to:
	45	+* Provide an additional 'transport type' to offer more means for creating a clustered setup;
	46	+* Provide clearer helptexts explaining which of the options is needed and what its effect is;
	47	+* Include validation on fields depending on the selected 'transport type'.
53	53
54		-
55	55	== **Fancy Forum Answers** ==
56	56
57	57	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:
58	58
59		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	53	+* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]
	54	+* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]
60	60
61		-== **Key takeaways** ==
	56	+== **Key Takeaways** ==
62	62
63	63	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:
64	64
...	...	@@ -66,10 +66,9 @@
66	66	* If you have feedback or ideas for us, talk to the Platypus
67	67	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
68	68	* Clear your browser cache (Ctrl + Shift + Del)
69		-* Check out the release notes [here]
	64	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
70	70	* Start thinking about how the license tracker can aid your development
71	71	* Start thinking about major, minor, and patch
72		-* Upgrade to the latest build number
73	73	* Keep making great integrations
74	74
75	75	Let's stay in touch and till next time!
...	...	@@ -77,6 +77,11 @@
77	77	{{info}}
78	78	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
79	79
80		-~*~* Indicates a next-generation-architecture only feature.
81		-{{/info}})))((({{toc/}}))){{/container}}
	74	+{{/info}}
	75	+)))
	76	+
	77	+(((
	78	+{{toc/}}
	79	+)))
82	82	{{/container}}
	81	+{{/container}}