Changes for page Customize Queue Alerting

Summary

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

Details

Page properties

Content

...	...	@@ -1,5 +1,5 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2		-In this microlearning, we will focus on how you can customize your queue alerts by configuring the trigger conditions and thresholds, which raise an alert and notify people when those points are passed. Should you want to learn more about the standard alerting that eMagiz offers, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]]. Note that the queue alerting explained in this page is only applicable for eMagiz models that are running the current generation runtime architecture.
	2	+In this microlearning, we will focus on how you can customize your queue alerting by setting up triggers on events and notifying people about them. Should you want to learn more about the standard alerting that eMagiz offers, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]].
3	3
4	4	Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5	5
...	...	@@ -9,19 +9,21 @@
9	9
10	10	== 2. Key concepts ==
11	11
12		-This microlearning focuses on customizing the queue alerts for each environment in your model. By customizing: we mean further configuring the trigger conditions and thresholds of your queues from the general default settings provided by eMagiz, so they better suit your needs and requirements.
	12	+This microlearning centers configuring dynamic alerting based on triggers you can define as a user.
	13	+By defining, we mean: Specifying based on what triggers an alert needs to be raised.
13	13
14		-* eMagiz applies the same set of triggers to all JMS queues
15		-* There are four queue trigger options that eMagiz currently provides:
16		-** Consumers check
17		-** Queue load check
18		-** Inactivity check
19		-** Periodic activity check
20		-* Recipients are defined on the queue level.
	15	+* There are five trigger options
	16	+** Error message
	17	+** Log message
	18	+** Queue consumers
	19	+** Messages in queue
	20	+** Queue throughput
	21	+* On the trigger level, the recipients are defined
	22	+* On the trigger level, the congestion control is defined
21	21
22		-== 3. Queue Alerting ==
	24	+== 3. Dynamic Alerting ==
23	23
24		-To enhance the observability of your integration landscape while running in the current generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers in your environment. On the top of the list, you will see all [["static" alerts>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] as defined by eMagiz below that you will see all "dynamic" alerts that you and your fellow team members (with sufficient rights) can view, edit and delete.
	26	+To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers in your environment. On the top of the list, you will see all [["static" alerts>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] as defined by eMagiz below that you will see all "dynamic" alerts that you and your fellow team members (with sufficient rights) can view, edit and delete.
25	25
26	26	We offer alerting on seven types.
27	27
...	...	@@ -143,9 +143,18 @@
143	143
144	144	== 4. Key takeaways ==
145	145
146		-* a
147		-* b
148		-* c
	148	+* There are seven trigger options
	149	+** Error message
	150	+** Log message
	151	+** Queue consumers
	152	+** Messages in queue
	153	+** Queue throughput
	154	+** Messages added to topic
	155	+** Topic consumer messages behind
	156	+* On the trigger level, the recipients are defined
	157	+* On the trigger level, the congestion control is defined
	158	+* Default configuration of the congestion control is sufficient in most cases
	159	+* When entering multiple external recipients, ensure each email address is separated with a comma
149	149
150	150	== 5. Suggested Additional Readings ==
151	151