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,13 +20,6 @@
20	20	** Queue consumers
21	21	** Messages in queue
22	22	** Queue throughput
23		--->
24		-{{/html}}
25		-* There are three trigger options
26		-** Error message
27		-** Log message
28		-** Messages added to topic
29		-** Topic consumer messages behind
30	30	* On the trigger level, the recipients are defined
31	31	* On the trigger level, the congestion control is defined
32	32
...	...	@@ -94,8 +94,14 @@
94	94
95	95	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.
96	96
97		-{{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]]
98	98
	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	+
99	99	Once you have selected the queue(s) and pressed "Select," eMagiz will close the pop-up and add the queues to the trigger.
100	100
101	101	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-in-queue-queue-selection-result.png]]
...	...	@@ -108,8 +108,18 @@
108	108
109	109	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.
110	110
111		-{{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]]
112	112
	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	+
113	113	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.
114	114
115	115	[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-occurence-config.png]]
...	...	@@ -122,7 +122,7 @@
122	122
123	123	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.
124	124
125		-{{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}}
126	126
127	127	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.
128	128
...	...	@@ -130,7 +130,7 @@
130	130
131	131	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.
132	132
133		-{{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}}
134	134
135	135	Once filled in, the solution should look similar as follows.
136	136