Changes for page Dynamic Alerting
Last modified by Danniar Firdausy on 2024/11/19 11:08
From version 47.1
edited by Erik Bakker
on 2024/08/26 12:05
on 2024/08/26 12:05
Change comment:
There is no comment for this version
To version 49.2
edited by Danniar Firdausy
on 2024/11/19 11:01
on 2024/11/19 11:01
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - Content
-
... ... @@ -12,26 +12,20 @@ 12 12 This microlearning centers on 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 -* There are four trigger options 16 -** Error message 15 +* There are three trigger options 17 17 ** Log message 18 18 ** Messages added to topic 19 19 ** Topic consumer messages behind 20 20 * On the trigger level, the recipients are defined 21 21 22 -{{html}} 23 -<!-- * On the trigger level, the congestion control is defined --> 24 -{{/html}} 25 - 26 26 == 3. Dynamic Alerting == 27 27 28 -To enhance the observability of your integration landscape while running in the current generation runtimearchitecture, 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.23 +To enhance the observability of your integration landscape while running in the current generation 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. 29 29 30 30 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. 31 31 32 -In this page, we offer dynamic alerting on four different types.27 +In this page, we offer dynamic alerting on three different types. 33 33 34 -* Error message 35 35 * Log message 36 36 * Messages added to topic 37 37 * Topic consumer messages behind ... ... @@ -42,6 +42,8 @@ 42 42 43 43 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). 44 44 39 +{{html}} 40 +<!-- 45 45 === 3.1 Error message === 46 46 47 47 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. ... ... @@ -49,6 +49,8 @@ 49 49 To define the trigger, fill in the header's name and the expected value. On top of that, you can fill in a description that will be added to the alert received via email. Once this is filled in, the configuration could look as follows. 50 50 51 51 [[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-error-message-configuration.png]] 48 +--> 49 +{{/html}} 52 52 53 53 === 3.2 Log message === 54 54 ... ... @@ -88,73 +88,9 @@ 88 88 89 89 {{info}}Note that to add the external recipients to these four alertings discussed in this microlearning, you first need to list them via the Manage->Alerting->Triggers->Notifications settings tab. To do that, please refer to this [[page>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Alerting.intermediate-alerting-setting-up-notifications-gen3||target="blank"]]{{/info}} 90 90 91 -{{html}} 92 -<!-- 93 -=== 3.3 Queue consumers === 94 - 95 -On top of the "static" alert that is autogenerated by eMagiz on Queue consumers, you can add additional "dynamic" alerts that only trigger when the number of consumers on a (specific) set of queues is below a certain threshold. 96 - 97 -To define the trigger, determine the threshold you want to check (i.e., 2). Subsequently, specify whether on which queues (or all queues) you want eMagiz to check for this condition. No further action is needed if you want to check on all queues. 98 - 99 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-all-queues.png]] 100 - 101 -You can uncheck the checkbox if you want to check on a specific (set of) queue(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove queues to the trigger. 102 - 103 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-specific-queues.png]] 104 - 105 -When you press the "Add" button, a new pop-up will appear through which you can select the queues for which you want the trigger to be activated. In this pop-up, you can choose one (or more) queues and press the "Select" button to add them to the trigger. 106 - 107 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-queue-selection.png]] 108 - 109 -{{info}}Note that when you want to select multiple queues at once, you cannot press "Enter" to Save your selection. In this case, you need to press the "Select" button to save your choice.{{/info}} 110 - 111 -Once you have selected the queue(s) and pressed "Select," eMagiz will close the pop-up and add the queues to the trigger. 112 - 113 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-queue-selection-result.png]] 114 - 115 -=== 3.4 Messages in queue === 116 - 117 -On top of the "static" alert that is autogenerated by eMagiz on Messages in a queue, you can add additional "dynamic" alerts that only trigger when a queue holds more than X messages. Logically, the X can be determined by the user. Subsequently, define whether on which queues (or all queues) you want eMagiz to check for this condition. No further action is needed if you want to check on all queues. 118 - 119 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-in-queue-all-queues.png]] 120 - 121 -You can uncheck the checkbox if you want to check on a specific (set of) queue(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove queues to the trigger. 122 - 123 -{{info}}This process of adding and removing specific queues works identically, as explained in the section on Queue consumers.[[Queue consumers.>>||anchor="H3.3Queueconsumers"]]{{/info}} 124 - 125 -Once you have selected the queue(s) and pressed "Select," eMagiz will close the pop-up and add the queues to the trigger. 126 - 127 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-in-queue-queue-selection-result.png]] 128 - 129 -=== 3.5 Queue througput === 130 - 131 -For this category you can add additional "dynamic" alerts that only trigger when the throughput on one or more queues is more or less than X messages per Y minutes. Subsequently, define whether on which queues (or all queues) you want eMagiz to check for this condition. No further action is needed if you want to check on all queues. 132 - 133 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-all-queues.png]] 134 - 135 -You can uncheck the checkbox if you want to check on a specific (set of) queue(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove queues to the trigger. 136 - 137 -{{info}}This process of adding and removing specific queues works identically, as explained in the section on Queue consumers.[[Queue consumers.>>||anchor="H3.3Queueconsumers"]]{{/info}} 138 - 139 -For this trigger, additional criteria can be configured that allow you to define when eMagiz needs to validate this configuration (i.e., Occurence). With the help of this configuration option, you can specify when the trigger needs to be evaluated. An example could be only on Monday between 04:00 AM and 05:00 AM. 140 - 141 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-occurence-config.png]] 142 - 143 -=== 3.6 Congestion control configuration === 144 - 145 -In the same "Output" tab, you can also define the congestion control configuration. The default configuration is that congestion control will be activated once more than ten alerts are triggered in the last ten minutes. So should you want to reduce this number, you can do so here. 146 - 147 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-congestion-control-config.png]] 148 - 149 -{{warning}}Note that we advise only reducing the number under the congestion control if the ten default is too high. We do **not** advise deactivating the congestion control as this can cause an explosion in the number of received notifications.{{/warning}} 150 - 151 ---> 152 -{{/html}} 153 - 154 154 == 4. Key takeaways == 155 155 156 -* There are four trigger options that eMagiz provides for dynamic alerting: 157 -** Error message 91 +* There are three trigger options that eMagiz provides for dynamic alerting: 158 158 ** Log message 159 159 ** Messages added to topic 160 160 ** Topic consumer messages behind ... ... @@ -161,12 +161,6 @@ 161 161 * On the trigger level, the recipients are defined. 162 162 * When entering multiple external recipients for these dynamic alerting triggers, ensure that you have listed them in the Manage->Alerting->Triggers->Notifications settings tab. 163 163 164 -{{html}} 165 -<!-- 166 -* On the trigger level, the congestion control is defined 167 -* Default configuration of the congestion control is sufficient in most cases 168 ---> 169 -{{/html}} 170 170 == 5. Suggested Additional Readings == 171 171 172 172 * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]