Changes for page Customize Queue Alerting

Summary

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

Details

Page properties

Content

...	...	@@ -41,21 +41,24 @@
41	41
42	42	* **Queue load check**
43	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	+
	45	+{{info}}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.{{/info}}
45	45
46	46	* **Inactivity check**
47	47	[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-inactivity-check.png]]
48		-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.
	49	+
	50	+{{info}}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.
49	49	** 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.
50	50	** 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.
51		-** In the example above, the trigger is set to evaluate from Monday to Friday, 9:00 to 17:00, and expects a message every four hours, an alert will be sent if no message is received by 13:00. However, if a message is received at 11:00, then the timer resets, and the next check will be at 15:00. If no message is received by then, an alert will be sent. Consequently, due to the configuration of expects a message every four hours, and considering that there are only two hours left until the configured 17:00, the trigger for the remaining two hours will not be executed.
	53	+** In the example above, the trigger is set to evaluate from Monday to Friday, 9:00 to 17:00, and expects a message every four hours, an alert will be sent if no message is received by 13:00. However, if a message is received at 11:00, then the timer resets, and the next check will be at 15:00. If no message is received by then, an alert will be sent. Consequently, due to the configuration of expects a message every four hours, and considering that there are only two hours left until the configured 17:00, the trigger for the remaining two hours will not be executed.{{/info}}
52	52
53	53	* **Periodic activity check**
54	54	[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-periodic-activity-check.png]]
55		-This trigger checks whether at least the specified number of messages is received during the specified interval. Similar to the others, you can also specify the instructions to be included in email notifications sent to recipients and in the alert message displayed in Manage->Alerting->Alerts.
	57	+
	58	+{{info}}This trigger checks whether at least the specified number of messages is received during the specified interval. Similar to the others, you can also specify the instructions to be included in email notifications sent to recipients and in the alert message displayed in Manage->Alerting->Alerts.
56	56	** If you enable this trigger, you must also specify the days of the week, the starting time, and the duration for the trigger to evaluate the queue. Additionally, you need to specify the minimum number of messages the queue is expected to receive. If this number is **not** reached, an alert will be generated.
57	57	** 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.
58		-** 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.
	61	+** 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}}
59	59
60	60	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".
61	61