Skip to Content

Changes for page Customize Queue Alerting

Last modified by Danniar Firdausy on 2024/09/04 15:45
From version 40.3
edited by Danniar Firdausy
on 2024/07/18 13:27
Change comment: There is no comment for this version
To version 40.7
edited by Danniar Firdausy
on 2024/07/18 14:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,8 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this microlearning, we will focus on how you can customize your queue alerts by configuring the trigger conditions and thresholds, which raise an alert and notify people when those points are passed.
2 +In this microlearning, we will focus on how you can customize your queue alerts by configuring the trigger conditions and thresholds, which raise an alert and notify people when those points are passed. Should you want to learn more about the standard alerting that eMagiz offers, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]]. Note that the queue alerting explained in this page is only applicable for eMagiz models that are running the current generation runtime architecture.
3 3  
4 -. Should you want to learn more about the standard alerting that eMagiz offers, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]].
5 -
6 6  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
8 8  == 1. Prerequisites ==
... ... @@ -11,21 +11,19 @@
11 11  
12 12  == 2. Key concepts ==
13 13  
14 -This microlearning centers configuring dynamic alerting based on triggers you can define as a user.
15 -By defining, we mean: Specifying based on what triggers an alert needs to be raised.
12 +This microlearning focuses on customizing the queue alerts for each environment 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.
16 16  
17 -* There are five trigger options
18 -** Error message
19 -** Log message
20 -** Queue consumers
21 -** Messages in queue
22 -** Queue throughput
23 -* On the trigger level, the recipients are defined
24 -* On the trigger level, the congestion control is defined
14 +* eMagiz applies the same set of triggers to all JMS queues
15 +* There are four queue trigger options that eMagiz currently provides:
16 +** Consumers check
17 +** Queue load check
18 +** Inactivity check
19 +** Periodic activity check
20 +* Recipients are defined on the queue level.
25 25  
26 -== 3. Dynamic Alerting ==
22 +== 3. Queue Alerting ==
27 27  
28 -To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers in your environment. On the top of the list, you will see all [["static" alerts>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] as defined by eMagiz below that you will see all "dynamic" alerts that you and your fellow team members (with sufficient rights) can view, edit and delete.
24 +To enhance the observability of your integration landscape while running in the current generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers in your environment. On the top of the list, you will see all [["static" alerts>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] as defined by eMagiz below that you will see all "dynamic" alerts that you and your fellow team members (with sufficient rights) can view, edit and delete.
29 29  
30 30  We offer alerting on seven types.
31 31  
... ... @@ -147,18 +147,9 @@
147 147  
148 148  == 4. Key takeaways ==
149 149  
150 -* There are seven trigger options
151 -** Error message
152 -** Log message
153 -** Queue consumers
154 -** Messages in queue
155 -** Queue throughput
156 -** Messages added to topic
157 -** Topic consumer messages behind
158 -* On the trigger level, the recipients are defined
159 -* On the trigger level, the congestion control is defined
160 -* Default configuration of the congestion control is sufficient in most cases
161 -* When entering multiple external recipients, ensure each email address is separated with a comma
146 +* a
147 +* b
148 +* c
162 162  
163 163  == 5. Suggested Additional Readings ==
164 164