Changes for page Dynamic Alerting

Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -9,11 +9,9 @@
9	9
10	10	== 2. Key concepts ==
11	11
12		-This microlearning centers on configuring dynamic alerting based on triggers you can define as a user.
	12	+This microlearning centers configuring dynamic alerting based on triggers you can define as a user.
13	13	By defining, we mean: Specifying based on what triggers an alert needs to be raised.
14	14
15		-{{html}}
16		-<!--
17	17	* There are five trigger options
18	18	** Error message
19	19	** Log message
...	...	@@ -20,15 +20,6 @@
20	20	** Queue consumers
21	21	** Messages in queue
22	22	** Queue throughput
23		--->
24		-{{/html}}
25		-* There are five trigger options
26		-** Error message
27		-** Log message
28		-** Queue consumers
29		-** Messages in queue
30		-** Queue throughput
31		-
32	32	* On the trigger level, the recipients are defined
33	33	* On the trigger level, the congestion control is defined
34	34
...	...	@@ -96,8 +96,14 @@
96	96
97	97	You can uncheck the checkbox if you want to check on a specific (set of) queue(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove queues to the trigger.
98	98
99		-{{info}}This process of adding and removing specific queues works identically, as explained in the section on Queue consumers.[[Queue consumers.>>||anchor="H3.3Queueconsumers"]]{{/info}}
	88	+[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-in-queue-specific-queues.png]]
100	100
	90	+When you press the "Add" button, a new pop-up will appear through which you can select the queues for which you want the trigger to be activated. In this pop-up, you can choose one (or more) queues and press the "Select" button to add them to the trigger.
	91	+
	92	+[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-queue-selection.png]]
	93	+
	94	+{{info}}Note that when you want to select multiple queues at once, you cannot press "Enter" to Save your selection. In this case, you need to press the "Select" button to save your choice.{{/info}}
	95	+
101	101	Once you have selected the queue(s) and pressed "Select," eMagiz will close the pop-up and add the queues to the trigger.
102	102
103	103	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-in-queue-queue-selection-result.png]]
...	...	@@ -110,8 +110,18 @@
110	110
111	111	You can uncheck the checkbox if you want to check on a specific (set of) queue(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove queues to the trigger.
112	112
113		-{{info}}This process of adding and removing specific queues works identically, as explained in the section on Queue consumers.[[Queue consumers.>>||anchor="H3.3Queueconsumers"]]{{/info}}
	108	+[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-specific-queues.png]]
114	114
	110	+When you press the "Add" button, a new pop-up will appear through which you can select the queues for which you want the trigger to be activated. In this pop-up, you can choose one (or more) queues and press the "Select" button to add them to the trigger.
	111	+
	112	+[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-queue-selection.png]]
	113	+
	114	+{{info}}Note that when you want to select multiple queues at once, you cannot press "Enter" to Save your selection. In this case, you need to press the "Select" button to save your choice.{{/info}}
	115	+
	116	+Once you have selected the queue(s) and pressed "Select," eMagiz will close the pop-up and add the queues to the trigger.
	117	+
	118	+[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-queue-selection-result.png]]
	119	+
115	115	For this trigger, additional criteria can be configured that allow you to define when eMagiz needs to validate this configuration (i.e., Occurence). With the help of this configuration option, you can specify when the trigger needs to be evaluated. An example could be only on Monday between 04:00 AM and 05:00 AM.
116	116
117	117	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-occurence-config.png]]
...	...	@@ -124,7 +124,7 @@
124	124
125	125	You can uncheck the checkbox to check on a specific (set of) topic(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove topics to the trigger.
126	126
127		-{{info}}This process of adding and removing specific topics works identically, as explained in the section on Queue consumers.[[Queue consumers.>>||anchor="H3.3Queueconsumers"]]{{/info}}
	132	+{{info}}This process of adding and removing specific topics works identically, as explained in the previous section on "Queue throughput." {{/info}}
128	128
129	129	For this trigger, additional criteria can be configured that allow you to define when eMagiz needs to validate this configuration (i.e., Occurence). With the help of this configuration option, you can specify when the trigger needs to be evaluated. An example could be only on Monday between 04:00 AM and 05:00 AM.
130	130
...	...	@@ -132,7 +132,7 @@
132	132
133	133	For this category, you can add additional "dynamic" alerts. These alerts only trigger when one (or more) consumer groups lag by X messages on one (or more) topic(s). Note that the default configuration is that you, as a user, need to specify for which topic(s) the alert applies, as consumers' behavior can vary widely.
134	134
135		-{{info}}This process of adding and removing specific topics works identically, as explained in the section on Queue consumers.[[Queue consumers.>>||anchor="H3.3Queueconsumers"]]{{/info}}
	140	+{{info}}This process of adding and removing specific topics works identically, as explained in the previous section on "Queue throughput." {{/info}}
136	136
137	137	Once filled in, the solution should look similar as follows.
138	138