Changes for page Customize Queue Alerting
Last modified by Danniar Firdausy on 2024/09/04 15:45
From version 49.1
edited by Erik Bakker
on 2024/07/25 09:12
on 2024/07/25 09:12
Change comment:
There is no comment for this version
To version 51.1
edited by Erik Bakker
on 2024/07/25 09:14
on 2024/07/25 09:14
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -34,16 +34,17 @@ 34 34 35 35 To customize these queue triggers to better suit your needs, you can click the edit buttons (green paper and pencil buttons) located at the end of each queue trigger. By doing so, you will get a pop-up page that allows you to further customize the conditions and thresholds of your queue triggers. 36 36 37 - * **Consumers check** 38 - [[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-consumers-check-queue.png]] 39 -This trigger checks how many processes (consumers) are subscribing to and retrieving messages from a particular queue over the last 10 minutes. It evaluates whether the number of consumers meets the specified threshold. If the number of consumers falls consistently **below** the "Expected consumers" value for a period of ten minutes, an alert is generated. You can customize this threshold as needed. Additionally, you can specify the instructions to be included in email notifications sent to recipients and in the alert message displayed in the Manage->Alerting->Alerts. 37 +* **Consumers check** 38 +[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-consumers-check-queue.png]] 40 40 41 - * **Queue load check** 42 - [[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-queue-load-check.png]] 43 -This trigger checks how many messages are produced on a particular queue and not yet retrieved by any consumers over the last 10 minutes. It evaluates whether the number of messages on the queue is below the specified threshold. If the number of messages is greater than the "Max messages queued" value, an alert is generated. You can customize this threshold as needed. Additionally, you can specify the instructions to be included in email notifications sent to recipients and in the alert message displayed in the Manage->Alerting->Alerts. It is important to note that if high bursts of messages occur regularly (e.g., during nightly batch processing, 1000 messages are expected to be produced to a certain queue), then setting a higher threshold (e.g., 1000 Max messages queued) can prevent false-positive alerts caused by more than 100 messages being queued during a duration of 10 minutes. 40 +{{info}}This trigger checks how many processes (consumers) are subscribing to and retrieving messages from a particular queue over the last ten minutes. It evaluates whether the number of consumers meets the specified threshold. If the number of consumers falls consistently **below** the "Expected consumers" value for a period of ten minutes, an alert is generated. You can customize this threshold as needed. Additionally, you can specify the instructions to be included in email notifications sent to recipients and in the alert message displayed in the Manage->Alerting->Alerts.{{/info}} 41 + 42 +* **Queue load check** 43 +[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-queue-load-check.png]] 44 +This trigger checks how many messages are produced on a particular queue and not yet retrieved by any consumers over the last ten minutes. It evaluates whether the number of messages on the queue is below the specified threshold. If the number of messages is consistently **greater** than the "Max messages queued" value for a period of ten minutes, an alert is generated. You can customize this threshold as needed. Additionally, you can specify the instructions to be included in email notifications sent to recipients and in the alert message displayed in the Manage->Alerting->Alerts. It is important to note that if high bursts of messages occur regularly (e.g., during nightly batch processing, 1000 messages are expected to be produced to a certain queue), then setting a higher threshold (e.g., 1000 Max messages queued) can prevent false-positive alerts caused by the default configuration. 44 44 45 - 46 - 46 +* **Inactivity check** 47 +[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-inactivity-check.png]] 47 47 This trigger checks whether a particular queue receives at least one message regularly or within a specified duration that you can configure. With this trigger, you specify whether you want to 'always' have the check running everyday or only during a specified time range. Additionally, you can specify the instructions to be included in email notifications sent to recipients and in the alert message displayed in the Manage->Alerting->Alerts. 48 48 ** If you select the "Always" option, the next step is to configure the "Expect a message every" period. This is useful if you want to be notified when your queue has not received at least one message within a specified time frame, such as a day or more. 49 49 ** If you select the "During time range" option, you can specify the days of the week and the starting time for the trigger to evaluate the queue. You will also need to specify the duration for which the trigger will evaluate and how frequently within that duration the queue should expect at least one message. Note that the "Expect a message every" setting must allow for at least two occurrences within the specified duration. If the queue receives a message before the end of the "Expect a message every" period, the timer will reset. This means that this trigger can produce two or more alerts a day.