Skip to Content

Changes for page Customize Queue Alerting

Last modified by Danniar Firdausy on 2024/09/04 15:45
From version 57.23
edited by Danniar Firdausy
on 2024/07/29 12:56
Change comment: There is no comment for this version
To version 57.25
edited by Danniar Firdausy
on 2024/07/29 13:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -69,11 +69,12 @@
69 69  * Unlike the Inactivity check, this Periodic Activity check evaluates only at **the end of each interval** and does **not** reset the timer when the minimum number of messages is reached during the interval. This means that this trigger will not produce more than one alert per day.
70 70  * In the example above, the trigger is set to evaluate from Monday to Friday, from 9:00 to 8:45 in the following morning, and expects a minimum of 100 messages within each interval. If the 100 messages are not received by that 8:45 in the next morning, an alert will be sent. Alternatively, if the 100 messages are reached, no alert will be generated for that interval, and the next check will start again at 9:00. For intervals starting on Friday, the next check will begin at 9:00 AM on Monday, as Saturday and Sunday are not included.{{/info}}
71 71  
72 -Upon saving, these custom values will apply immediately, putting the new check into effect. Additionally, you will notice that the "Settings" status of the queue trigger you just customized has changed from "Default" to "Custom".
72 +Upon saving, these custom values will apply immediately, putting the new check into effect. Additionally, you will notice that the "Settings" status of the queue trigger you just customized has changed from "Default" to "Custom". Similarly, on this page, you can also find the "Notifications" tab that allows you to configure which recipients that you want to receive the notifications from the alerting of a specific queue. If you want to learn more about this notifications and how to configure it, please refer to this [[microlearning>>Main.eMagiz Academy.Microlearnings.Intermediate Level.Alerting.intermediate-alerting-setting-up-notifications-gen3||target="blank"]].
73 73  
74 74  == 4. Key takeaways ==
75 75  
76 -* Queue alerting involves setting triggers for all queues in your model, which can be customized for individual queues or modified as default values.
76 +* Queue alerting involves applying a uniform set of triggers to all queues in your model.
77 +* As a user with the edit rights in Manage of a particular environment, you can modify the default values for all of your queue triggers or customize the trigger configurations of individual queues.
77 77  * eMagiz provides four queue trigger options: Consumers Check (monitoring the number of processes consuming messages), Queue Load Check (monitoring the number of queued messages), Inactivity Check (ensuring regular received message), and Periodic Activity Check (ensuring a minimum number of messages within a specified interval).
78 78  * If you want to learn more on how to configure the recipients for the alerts generated from these queue triggers, please check out [[Setting up notification>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Alerting.intermediate-alerting-setting-up-notifications-gen3||target="blank"]].
79 79