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.1
edited by Erik Bakker
on 2023/05/27 14:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Content
... ... @@ -9,11 +9,9 @@
9 9  
10 10  == 2. Key concepts ==
11 11  
12 -This microlearning centers on configuring dynamic alerting based on triggers you can define as a user.
12 +This microlearning centers configuring dynamic alerting based on triggers you can define as a user.
13 13  By defining, we mean: Specifying based on what triggers an alert needs to be raised.
14 14  
15 -{{html}}
16 -<!--
17 17  * There are five trigger options
18 18  ** Error message
19 19  ** Log message
... ... @@ -20,26 +20,20 @@
20 20  ** Queue consumers
21 21  ** Messages in queue
22 22  ** Queue throughput
23 --->
24 -{{/html}}
25 -* There are four trigger options
26 -** Error message
27 -** Log message
28 -** Messages added to topic
29 -** Topic consumer messages behind
30 30  * On the trigger level, the recipients are defined
31 31  * On the trigger level, the congestion control is defined
32 32  
33 33  == 3. Dynamic Alerting ==
34 34  
35 -To enhance the observability of your integration landscape while running in the current generation runtime architecture, we provide a functionality in the 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. From there on, you can navigate to the "Other" tab.
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.
36 36  
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.
28 +We offer alerting on seven types.
38 38  
39 -In this page, we offer alerting on four types.
40 -
41 41  * Error message
42 42  * Log message
32 +* Queue consumers
33 +* Messages in queue
34 +* Queue throughput
43 43  * Messages added to topic
44 44  * Topic consumer messages behind
45 45  
... ... @@ -47,8 +47,6 @@
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.