Changes for page Customize Queue Alerting
Last modified by Danniar Firdausy on 2024/09/04 15:45
From version 40.8
edited by Danniar Firdausy
on 2024/07/18 14:46
on 2024/07/18 14:46
Change comment:
There is no comment for this version
To version 40.9
edited by Danniar Firdausy
on 2024/07/18 15:01
on 2024/07/18 15:01
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -21,10 +21,19 @@ 21 21 22 22 == 3. 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 present in the Create phase of your model.Thismeans thatallofthese queues by defaulthave triggersconfigured forthem. eMagiz24 +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 25 26 -However, as a user, you can also further customize the trigger condition and thresholds for each of these queues. 27 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 + 28 28 == 3.1 Customize Queue Alerting == 29 29 30 30