Changes for page Customize Queue Alerting

Last modified by Danniar Firdausy on 2024/09/04 15:45

From version 43.22
edited by Danniar Firdausy
on 2024/07/22 15:56
Change comment: There is no comment for this version
To version 43.38
edited by Danniar Firdausy
on 2024/07/23 11:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -12,7 +12,7 @@
12 12  
13 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.
14 14  
15 -* eMagiz applies the same set of triggers to all JMS queues
15 +* eMagiz applies the same set of triggers to all JMS queues.
16 16  * There are four queue trigger options that eMagiz currently provides:
17 17  ** Consumers check
18 18  ** Queue load check
... ... @@ -32,20 +32,22 @@
32 32  
33 33  To customize these queue triggers to better suit your needs, you can click the edit buttons (green paper and pencil buttons) that find 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.
34 34  
35 - * Consumers check
35 + * **Consumers check**
36 36   [[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-consumers-check-queue.png]]
37 +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 below the "Expected consumers" 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.
37 37  
38 -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 below the "Expected consumers" 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 during the manage phase.
39 -
40 - * Queue load check
39 + * **Queue load check**
41 41   [[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-queue-load-check.png]]
42 - aa
41 +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.
43 43  
44 - * Inactivity check
43 + * **Inactivity check**
45 45   [[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-inactivity-check.png]]
46 - aa
45 +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.
46 +If you select the Always option, then the next thing you need to configure is the Expect a message every a certain period of time. This can be useful if you want to be notified when your queue has not received at least one message within a day or more days.
47 +
48 +If you select the During time range option, you can select in which days of the week the trigger will evaluate and starting from what time of those selected days it will start evaluating. With this, you will need to specify for how long is the duration that the trigger will be evaluating as well as every how often within that duration that the queue expects at least a message. Note that this "Expect a message every" configuration requires that it should fit at least 2 times occurances in the duration.
47 47  
48 - * Periodic activity check
50 + * **Periodic activity check**
49 49   [[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-periodic-activity-check.png]]
50 50   aa
51 51