Changes for page Customize Queue Alerting

Summary

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

Details

Page properties

Content

...	...	@@ -6,10 +6,11 @@
6	6	== 1. Prerequisites ==
7	7
8	8	* Basic knowledge of the eMagiz platform
	9	+* Basic knowledge of alerting in the eMagiz platform
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.
	13	+This microlearning focuses on customizing the queue alerts for each environment (i.e., Testing-Acceptance-Production) 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.
13	13
14	14	* eMagiz applies the same set of triggers to all JMS queues
15	15	* There are four queue trigger options that eMagiz currently provides:
...	...	@@ -19,25 +19,14 @@
19	19	** Periodic activity check
20	20	* Recipients are defined on the queue level.
21	21
22		-== 3. Queue Alerting ==
	23	+== 3. Customize Queue Alerting ==
23	23
24		-In principle, queue alerting refers to the configuration of alerts that work by applying a uniform set of triggers to all queues in your model. By queues here, we mean all queues that are generated by eMagiz and existing in the Create phase of your model. By default, eMagiz configures triggers for all these queues using values based on the environment's topology. However, as a user, you can customize these default values to better suit your model's requirements, as well as modify the trigger conditions and thresholds for each queue.
	25	+In principle, queue alerting refers to the configuration of alerts that work by applying a uniform set of triggers to all queues in your model. By queues here, we mean all queues that are generated by eMagiz and existing in the Create phase of your model. Out-of-the-box, eMagiz provides the default values that are suitable for the topology of each of your model environments (Testing-Acceptance-Production). By topology here, we refer whether your environment is running on single-lane or double-lane setup. In the screenshot below, you can find the overview of your queue alerts by navigating to Manage -> Alerting -> Triggers. Here, you will find all the queues that are generated by eMagiz and currently existing in the Create phase of your model.
25	25
	27	+[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz-queue-alerts-overview.png]]
26	26
	29	+However, as a user, you can customize these default values to better suit your model's requirements, as well as modify the trigger conditions and thresholds for each queue. To customize the default values that eMagiz has configured by default, you can click the "Configure defaults" button on top of this list. You will see
27	27
28		-
29		-
30		-
31		-
32		-
33		-
34		-
35		-a uniform set of triggers to all queues in your model. By queues here, we mean all queues that are generated by eMagiz and existing in the Create phase of your model. This means that all of these queues by default have triggers configured by eMagiz for them. eMagiz has provided the default values for these triggers that is based on the topology of the environment. However, as a user, you can also further customize this default values to be better suited to the requirements of your model, as well as further customize the trigger condition and thresholds for each of the queues.
36		-
37		-== 3.1 Customize Queue Alerting ==
38		-
39		-
40		-
41	41	== 4. Key takeaways ==
42	42
43	43	* a