Changes for page Topic Alerting

Summary

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

Details

Page properties

Content

...	...	@@ -47,37 +47,24 @@
47	47	Next to customizing the default values for all topic triggers, you can also modify the trigger configurations for individual topics. To customize these topic triggers to better suit your needs, you can click the edit buttons (green paper and pencil buttons) located at the end of each topic trigger. By doing so, you will get a pop-up page that allows you to further customize the conditions and thresholds of your topic triggers, which will be discussed in the following.
48	48
49	49	==== 3.2.1 Minimum throughput check ====
50		-[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-consumers-check-queue.png]]
51	51
52		-{{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}}
	51	+[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-topic-alerting--minimum-throughput-check.png]]
53	53
54		-* **Queue load check**
55		-[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-queue-load-check.png]]
	53	+{{info}}This alert checks whether a topic receives at least the specified number of messages within a 10-minute window. If the count remains below the threshold for the entire window, a Problem alert is triggered. Please provide the threshold that suites the integration. 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}}
56	56
57		-{{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 measures the number of messages on the queue. If the number of messages is consistently **greater** than the threshold value (i.e., "Max messages queued") for a period of ten minutes, an alert is generated. Otherwise, no alert will be 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}}
	55	+==== 3.2.2 Messages behind check ====
58	58
59		-* **Inactivity check**
60		-[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-inactivity-check.png]]
	57	+[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-topic-alerting--messages-behind-check.png]]
61	61
62		-{{info}}This trigger checks whether a particular queue receives at least one message regularly or within the specified time frame. With this trigger, you specify whether you want to 'always' have the check running everyday or only during a specified time range. If the queue receives a message within a specified time frame (i.e., time frame specified in the 'Expect a message every'), then the timer will reset and the next evaluation interval will start. Therefore, this trigger can produce two or more alerts a day if that setting is set to less than half a day. Similar to the other triggers, 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.
63		-* 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 run the check every day and be notified when your queue has not received at least one message within a specified time frame, such as within an hour, a day or more.
64		-* 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 for this option, the "Expect a message every" setting must allow for at least two occurrences within the specified duration.
65		-* 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}}
	59	+{{info}}This alert monitors consumer lag and triggers a Problem alert if any consumer group exceeds the defined threshold for 10 consecutive minutes. Please provide the threshold that suites the integration. For more information check out the helptext on the component{{/info}}
66	66
67		-* **Periodic activity check**
68		- [[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-periodic-activity-check.png]]
69	69
70		-{{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.
71		-* 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.
72		-* 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.
73		-* 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}}
	62	+{{info}}Upon saving, these custom values will apply immediately, putting the new check into effect. Additionally, you will notice that the "Settings" status of the topic 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 topic. 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"]].{{/info}}
74	74
75		-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"]].
76		-
77	77	== 4. Key takeaways ==
78	78
79		-* 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.
80		-* 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).
	66	+* As a user with the edit rights in Manage of a particular environment, you can modify the default values for all of your topic triggers or customize the trigger configurations of individual topics.
	67	+* eMagiz provides four topic trigger options: Minimum throughput check (monitoring the number of messages processed by the topic), Messages behind check (monitoring the consumer lag).
81	81	* Once you save your trigger configurations, they will take effect immediately.
82	82
83	83	== 5. Suggested Additional Readings ==
...	...	@@ -89,5 +89,5 @@
89	89	* [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
90	90	** [[Alerting (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Alerting.WebHome||target="blank"]]
91	91	*** [[Setting up notifications (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Alerting.intermediate-alerting-setting-up-notifications-gen3||target="blank"]]
92		-* [[Queue Alerting (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22queue+alerting%22||target="blank"]]
	79	+* [[Topic Alerting (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22topic+alerting%22||target="blank"]]
93	93	)))((({{toc/}}))){{/container}}{{/container}}