Skip to Content

Changes for page Dynamic Alerting

Last modified by Danniar Firdausy on 2024/11/19 11:08
From version 39.15
edited by Danniar Firdausy
on 2024/07/29 14:22
Change comment: There is no comment for this version
To version 39.16
edited by Danniar Firdausy
on 2024/07/29 14:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -43,12 +43,12 @@
43 43  * Messages added to topic
44 44  * Topic consumer messages behind
45 45  
46 +{{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}}
47 +
46 46  [[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-trigger-options.png]]
47 47  
48 48  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).
49 49  
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 -
52 52  === 3.1 Error message ===
53 53  
54 54  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.