Changes for page Dynamic Alerting

Last modified by Danniar Firdausy on 2024/11/19 11:08

From 23.1 to 22.1 From 39.4 to 39.3

From version 39.3

edited by Danniar Firdausy
on 2024/07/29 13:59

Change comment: There is no comment for this version

To version 23.1

edited by Erik Bakker
on 2022/06/10 09:47

Change comment: Deleted image "novice-alerting-linking-tags-to-triggers--example-trigger-detail-one-tag.png"

Raw
Rendered

Summary

Page properties (5 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- novice-alerting-linking-tags-to-triggers--example-trigger-detail-select-tag.png

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Dynamic Alerting
++Linking Tag(s) to Trigger(s)

Parent

@@ -1,1 +1,1 @@
--Main.eMagiz Academy.Microlearnings.Novice.Alerting.WebHome
++WebHome

Author

@@ -1,1 +1,1 @@
--XWiki.dfirdausy
++XWiki.ebakker

Default language

...	...	@@ -1,1 +1,0 @@
1		-en

Content

@@ -1,8 +1,12 @@
  {{container}}{{container layoutStyle="columns"}}(((
--In this microlearning, we will focus on how you can configure your dynamic 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"]].
++In this microlearning, we will focus on how you can link your alerting tag(s) to alerting trigger(s).
++In a previous microlearning we already discussed parts of this. In this microlearning we will zoom in on the Trigger section of Alerting.
  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
++* Last update: April 1th 2021
++* Required reading time: 5 minutes
++
  == 1. Prerequisites ==
  * Basic knowledge of the eMagiz platform
@@ -9,168 +9,65 @@
  == 2. Key concepts ==
--This microlearning centers on configuring dynamic alerting based on triggers you can define as a user.
--By defining, we mean: Specifying based on what triggers an alert needs to be raised.
++This microlearning centers around linking tag(s) to trigger(s).
++With linking, we mean: Categorize a certain trigger with the help of tag functionality
--{{html}}
--<!--
--* There are five trigger options
--** Error message
--** Log message
--** Queue consumers
--** Messages in queue
--** Queue throughput
---->
--{{/html}}
--* There are five trigger options
--** Error message
--** Log message
--** Queue consumers
--** Messages in queue
--** Queue throughput
++* Make tags descriptive in nature
++* Re-use tags over multiple triggers that have the same aim
++* In case of a start, daily and end alert use the same tag for all of them
--* On the trigger level, the recipients are defined
--* On the trigger level, the congestion control is defined
--== 3. Dynamic Alerting ==
--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.
++== 3. Linking Tag(s) to Trigger(s) ==
--We offer alerting on seven types.
++In our previous dalliance with this subject we already discussed parts of what we will discuss in this microlearning. This microlearning is mainly meant to reiterate the importance of using proper tags when setting up your alerting. Linking the correct tag(s) to your trigger(s) will help you to clarify how the alerting structure for your project is set up. This is not only nice when you want to revisit the alerting section but it is also very usefull in communication with the business and with a support desk. This way you can create a common truth surrounding a common language. Key parts in achieving this are:
--* Error message
--* Log message
--* Queue consumers
--* Messages in queue
--* Queue throughput
--* Messages added to topic
--* Topic consumer messages behind
++* Make tags descriptive in nature
++* Re-use tags over multiple triggers that have the same aim
++* In case of a start, daily and end alert use the same tag for all of them
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-trigger-options.png]]
++To link tag(s) to trigger(s) you navigate to Manage -> Alerting -> Triggers
--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).
++In this overview you can simply select a specific trigger to see the detailed configuration of the trigger. Depending on the type of trigger that you open the avaiable tabs within the pop-up and the information shown in the pop-up can differ. Below we show two distinct examples:
--=== 3.1 Error message ===
++[[image:Main.Images.Microlearning.WebHome@novice-alerting-linking-tags-to-triggers--example-trigger-detail-data-measurements.png]]
--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.
++[[image:Main.Images.Microlearning.WebHome@novice-alerting-linking-tags-to-triggers--example-trigger-detail-log-entry.png]]
--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.
++As you can see from these examples is that the number of tabs within the pop-up differ. The first tab is were the configuration of the trigger happens. In all the other tabs you need to link the tag(s) to the trigger. To do so simply press Add in one of these tabs, search for the Tag you want to link to this trigger, select it and press Select.
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-error-message-configuration.png]]
++[[image:Main.Images.Microlearning.WebHome@novice-alerting-linking-tags-to-triggers--example-trigger-detail-no-tag.png]]
--=== 3.2 Log message ===
++[[image:Main.Images.Microlearning.WebHome@novice-alerting-linking-tags-to-triggers--example-trigger-detail-select-tag.png]]
--On top of the "static" alert that is autogenerated by eMagiz on Log messages, you can add additional "dynamic" alerts that only trigger when a log message contains a specific phrase. This is likely when you log something on which you want to alert when it happens.
++[[image:Main.Images.Microlearning.WebHome@novice-alerting-linking-tags-to-triggers--example-trigger-detail-one-tag.png]]
--To define the trigger, fill in the phrase you want to check. 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.
++When you are happy with your selection you can press Save on trigger level and eMagiz will link the tag to the trigger.
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-log-message-configuration.png]]
--=== 3.3 Queue consumers ===
--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.
++== 4. Assignment ==
--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.
++Link an (extra) tag to a trigger.
++This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-all-queues.png]]
++== 5. Key takeaways ==
--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.
++* Assist in creating a common language
++* Make tags descriptive in nature
++* Re-use tags over multiple triggers that have the same aim
++* In case of a start, daily and end alert use the same tag for all of them
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-specific-queues.png]]
--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.
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-queue-selection.png]]
++== 6. Suggested Additional Readings ==
--{{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}}
++If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
--Once you have selected the queue(s) and pressed "Select," eMagiz will close the pop-up and add the queues to the trigger.
++== 7. Silent demonstration video ==
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-consumers-queue-selection-result.png]]
++This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
--=== 3.4 Messages in queue ===
++{{video attachment="novice-alerting-linking-tags-to-triggers.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
--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.
--
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-in-queue-all-queues.png]]
--
--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.
--
--{{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}}
--
--Once you have selected the queue(s) and pressed "Select," eMagiz will close the pop-up and add the queues to the trigger.
--
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-in-queue-queue-selection-result.png]]
--
--=== 3.5 Queue througput ===
--
--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.
--
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-all-queues.png]]
--
--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.
--
--{{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}}
--
--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.
--
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-queue-throughput-occurence-config.png]]
--
--=== 3.6 Messages added to topic ===
--
--For this category, you can add additional "dynamic" alerts. These alerts only trigger when the messages added to one or more topic is less than X messages per Y minutes. On top of the number of messages (X) and the timeframe (Y), you can define whether to validate this on a specific topic or all topics. Note that the default configuration is that the alert applies to all topics.
--
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-messages-added-to-topic-all-topics.png]]
--
--You can uncheck the checkbox to check on a specific (set of) topic(s). As a result, the "Add" and "Remove" buttons are displayed by eMagiz, through which you can add and remove topics to the trigger.
--
--{{info}}This process of adding and removing specific topics works identically, as explained in the section on Queue consumers.[[Queue consumers.>>||anchor="H3.3Queueconsumers"]]{{/info}}
--
--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.
--
--=== 3.7 Topic consumer lag ===
--
--For this category, you can add additional "dynamic" alerts. These alerts only trigger when one (or more) consumer groups lag by X messages on one (or more) topic(s). Note that the default configuration is that you, as a user, need to specify for which topic(s) the alert applies, as consumers' behavior can vary widely.
--
--{{info}}This process of adding and removing specific topics works identically, as explained in the section on Queue consumers.[[Queue consumers.>>||anchor="H3.3Queueconsumers"]]{{/info}}
--
--Once filled in, the solution should look similar as follows.
--
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-topic-consumer-lag-selected-topics.png]]
--
--=== 3.8 Recipient(s) configuration ===
--
--You can select your recipients when you switch from the "Trigger" to the "Output" tab. In this overview, you can choose both eMagiz users and external recipients.
--
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-recipient-config.png]]
--
--{{info}}Note that when you define multiple external recipients, you need to separate each email address with a comma to make it work.{{/info}}
--
--=== 3.9 Congestion control configuration ===
--
--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.
--
--[[image:Main.Images.Microlearning.WebHome@novice-alerting-dynamic-alerting--dynamic-alert-congestion-control-config.png]]
--
--{{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}}
--
--== 4. Key takeaways ==
--
--* There are seven trigger options
--** Error message
--** Log message
--** Queue consumers
--** Messages in queue
--** Queue throughput
--** Messages added to topic
--** Topic consumer messages behind
--* On the trigger level, the recipients are defined
--* On the trigger level, the congestion control is defined
--* Default configuration of the congestion control is sufficient in most cases
--* When entering multiple external recipients, ensure each email address is separated with a comma
--
--== 5. Suggested Additional Readings ==
--
--If you are interested in this topic and want more information, please read the help text provided by eMagiz.
--
  )))((({{toc/}}))){{/container}}{{/container}}

novice-alerting-linking-tags-to-triggers--example-trigger-detail-select-tag.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ebakker

Size

...	...	@@ -1,0 +1,1 @@
	1	+11.7 KB

Content

Changes for page Dynamic Alerting

Summary

Details

Navigation