Skip to Content

Changes for page Customize Queue Alerting

Last modified by Danniar Firdausy on 2024/09/04 15:45
From version 40.2
edited by Danniar Firdausy
on 2024/07/18 13:20
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,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this microlearning, we will focus on how you can customize your queue alerting by setting up triggers on events and notifying people about them. 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"]].
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 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -9,21 +9,19 @@
9 9  
10 10  == 2. Key concepts ==
11 11  
12 -This microlearning centers configuring dynamic alerting based on triggers you can define as a user.
13 -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.
14 14  
15 -* There are five trigger options
16 -** Error message
17 -** Log message
18 -** Queue consumers
19 -** Messages in queue
20 -** Queue throughput
21 -* On the trigger level, the recipients are defined
22 -* 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.
23 23  
24 -== 3. Dynamic Alerting ==
22 +== 3. Queue Alerting ==
25 25  
26 -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.
27 27  
28 28  We offer alerting on seven types.
29 29  
... ... @@ -145,18 +145,9 @@
145 145  
146 146  == 4. Key takeaways ==
147 147  
148 -* There are seven trigger options
149 -** Error message
150 -** Log message
151 -** Queue consumers
152 -** Messages in queue
153 -** Queue throughput
154 -** Messages added to topic
155 -** Topic consumer messages behind
156 -* On the trigger level, the recipients are defined
157 -* On the trigger level, the congestion control is defined
158 -* Default configuration of the congestion control is sufficient in most cases
159 -* When entering multiple external recipients, ensure each email address is separated with a comma
146 +* a
147 +* b
148 +* c
160 160  
161 161  == 5. Suggested Additional Readings ==
162 162