Skip to Content

Changes for page Dynamic Alerting

Last modified by Danniar Firdausy on 2024/11/19 11:08
From version 39.12
edited by Danniar Firdausy
on 2024/07/29 14:15
Change comment: There is no comment for this version
To version 39.13
edited by Danniar Firdausy
on 2024/07/29 14:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -36,13 +36,10 @@
36 36  
37 37  Here, 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"]] that are defined by eMagiz (alerts that are non-editable). And, below that (alerts that are editable), you will see all "dynamic" alerts that you and your fellow team members (with sufficient rights) can view, edit and delete.
38 38  
39 -We offer alerting on seven types.
39 +We offer alerting on four types.
40 40  
41 41  * Error message
42 42  * Log message
43 -* Queue consumers
44 -* Messages in queue
45 -* Queue throughput
46 46  * Messages added to topic
47 47  * Topic consumer messages behind
48 48  
... ... @@ -50,6 +50,8 @@
50 50  
51 51  First, we will discuss the configuration of each trigger type. Subsequently, we will discuss defining which recipients will be notified and how to alter the default congestion control settings (as this is the same for each trigger type).
52 52  
50 +{{info}}As of the recent eMagiz release, we have moved the configurations for queue triggers (i.e., Queue consumers, Messages in queue, Queue throughput) to another page. Please refer to the [[Customize Queue alerting>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-customize-queue-alerting.WebHome||target="blank"]] page if you want to learn more on how to customize the triggers for these queues or the default values of these queue triggers.{{/info}}
51 +
53 53  === 3.1 Error message ===
54 54  
55 55  On top of the "static" alert that is autogenerated by eMagiz on Error messages, you can add additional "dynamic" alerts that only trigger when an error message is raised for which a specific header contains a particular value. This is most likely relevant when a specific error message with certain characteristics (i.e., a particular header value) needs to be sent to a different set of recipients.