Skip to Content

Changes for page Customize Queue Alerting

Last modified by Danniar Firdausy on 2024/09/04 15:45
From version 43.12
edited by Danniar Firdausy
on 2024/07/22 13:28
Change comment: There is no comment for this version
To version 21.1
edited by Erik Bakker
on 2022/06/10 09:47
Change comment: Deleted image "novice-alerting-linking-tags-to-triggers--example-trigger-detail-log-entry.png"

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Customize Queue Alerting
1 +Linking Tag(s) to Trigger(s)
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.eMagiz Academy.Microlearnings.Novice.Alerting.WebHome
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.ebakker
Default language
... ... @@ -1,1 +1,0 @@
1 -en
Content
... ... @@ -1,56 +1,77 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this microlearning, we will focus on how you can customize your queue alerts by configuring the trigger conditions and thresholds, which raise an alert and notify people when those points are passed. 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"]]. Note that the queue alerting explained in this page is only applicable for eMagiz models that are running the current generation runtime architecture.
2 +In this microlearning, we will focus on how you can link your alerting tag(s) to alerting trigger(s).
3 +In a previous microlearning we already discussed parts of this. In this microlearning we will zoom in on the Trigger section of Alerting.
3 3  
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
7 +* Last update: April 1th 2021
8 +* Required reading time: 5 minutes
9 +
6 6  == 1. Prerequisites ==
7 7  
8 8  * Basic knowledge of the eMagiz platform
9 -* Basic knowledge of alerting in the eMagiz platform
10 10  
11 11  == 2. Key concepts ==
12 12  
13 -This microlearning focuses on customizing the queue alerts for each environment (i.e., Testing-Acceptance-Production) in your model. By customizing: we mean further configuring the trigger conditions and thresholds of your queues from the general default settings provided by eMagiz, so they better suit your needs and requirements.
16 +This microlearning centers around linking tag(s) to trigger(s).
17 +With linking, we mean: Categorize a certain trigger with the help of tag functionality
14 14  
15 -* eMagiz applies the same set of triggers to all JMS queues
16 -* There are four queue trigger options that eMagiz currently provides:
17 -** Consumers check
18 -** Queue load check
19 -** Inactivity check
20 -** Periodic activity check
21 -* Recipients are defined on the queue level.
19 +* Make tags descriptive in nature
20 +* Re-use tags over multiple triggers that have the same aim
21 +* In case of a start, daily and end alert use the same tag for all of them
22 22  
23 -== 3. Queue Alerting ==
24 -=== 3.1 Queue Alerting Overview ===
25 -In principle, queue alerting refers to the configuration of alerts that work by applying a uniform set of triggers to all queues in your model. By queues here, we mean all queues that are generated by eMagiz and existing in the Create phase of your model. Out-of-the-box, eMagiz provides the default values that are suitable for the topology of each of your model environments (Testing-Acceptance-Production). By topology here, we refer whether your environment is running on single-lane or double-lane setup. In the screenshot below, you can find the overview of your queue alerts by navigating to Manage -> Alerting -> Triggers.
26 26  
27 -[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz-queue-alerts-overview.png]]
28 28  
29 -Here, you will find all the queues that are generated by eMagiz and currently existing in the Create phase of your model, along with the trigger conditions and thresholds that are applied to each of these queues. In the following sections, we will discuss how you can tune these queue triggers to your needs.
25 +== 3. Linking Tag(s) to Trigger(s) ==
30 30  
31 -=== 3.2 Customize Queue Alerting ===
27 +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:
32 32  
33 -To customize these queue triggers to better suit your needs, you can click the edit buttons (green paper and pencil buttons) that find at the end of each queue trigger. By doing so, you will see the pop-up page as shown below as an example.
29 +* Make tags descriptive in nature
30 +* Re-use tags over multiple triggers that have the same aim
31 +* In case of a start, daily and end alert use the same tag for all of them
34 34  
35 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-consumers-check-queue-load-check.png]]
33 +To link tag(s) to trigger(s) you navigate to Manage -> Alerting -> Triggers
36 36  
35 +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:
37 37  
38 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-customize-queue-alerting-inactivity-check-periodic-activity-check.png]]
37 +[[image:Main.Images.Microlearning.WebHome@novice-alerting-linking-tags-to-triggers--example-trigger-detail-data-measurements.png]]
39 39  
40 -=== 3.3 Customize Default Values ===
39 +[[image:Main.Images.Microlearning.WebHome@novice-alerting-linking-tags-to-triggers--example-trigger-detail-log-entry.png]]
41 41  
42 -Next to that, you can also customize the default values of your queue triggers to better suit the requirements of each environment of your model, as well as modify the trigger conditions and thresholds for each queue. To customize the default values that eMagiz has configured by default, you can click the "Configure defaults" button on top of this list. You will see
41 +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.
43 43  
44 -The "Configure defaults" button above the list of these queue triggers (or "View defaults" depending if your account does not have the edit rights on Manage) to customize the default values of your queue triggers
43 +[[image:Main.Images.Microlearning.WebHome@novice-alerting-linking-tags-to-triggers--example-trigger-detail-no-tag.png]]
45 45  
46 -== 4. Key takeaways ==
45 +[[image:Main.Images.Microlearning.WebHome@novice-alerting-linking-tags-to-triggers--example-trigger-detail-select-tag.png]]
47 47  
48 -* a
49 -* b
50 -* c
47 +[[image:Main.Images.Microlearning.WebHome@novice-alerting-linking-tags-to-triggers--example-trigger-detail-one-tag.png]]
51 51  
52 -== 5. Suggested Additional Readings ==
49 +When you are happy with your selection you can press Save on trigger level and eMagiz will link the tag to the trigger.
53 53  
54 -If you are interested in this topic and want more information, please read the help text provided by eMagiz.
55 55  
52 +
53 +== 4. Assignment ==
54 +
55 +Link an (extra) tag to a trigger.
56 +This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
57 +
58 +== 5. Key takeaways ==
59 +
60 +* Assist in creating a common language
61 +* Make tags descriptive in nature
62 +* Re-use tags over multiple triggers that have the same aim
63 +* In case of a start, daily and end alert use the same tag for all of them
64 +
65 +
66 +
67 +== 6. Suggested Additional Readings ==
68 +
69 +If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
70 +
71 +== 7. Silent demonstration video ==
72 +
73 +This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
74 +
75 +{{video attachment="novice-alerting-linking-tags-to-triggers.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
76 +
56 56  )))((({{toc/}}))){{/container}}{{/container}}
novice-alerting-linking-tags-to-triggers--example-trigger-detail-no-tag.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ebakker
Size
... ... @@ -1,0 +1,1 @@
1 +6.3 KB
Content
novice-alerting-linking-tags-to-triggers--example-trigger-detail-one-tag.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ebakker
Size
... ... @@ -1,0 +1,1 @@
1 +9.1 KB
Content
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