Wiki source code of Standard Alerting eMagiz

Last modified by Erik Bakker on 2024/02/20 08:25
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}(((
3
4 Assessing the health of your systems is critical in a stable and robust integration solution.
5 Getting alerts when something deviates is crucial to guarantee a stable and robust integration solution.
6
7 In this microlearning, we will educate you on Alerting within the Manage phase of eMagiz.
8
9 == 1. Prerequisites ==
10
11 * Basic knowledge of the eMagiz platform
12
13 == 2. Key concepts ==
14
15 This microlearning centers around setting up the alerting in eMagiz.
16 With alerting, we mean: Configuring thresholds that raise an alert when the point is passed.
17
18 There are three areas in which alerting is configured for you by eMagiz:
19
20 * Error Messages
21 * Measurement Data
22 * Missing Data
23
24 From eMagiz, we provide a standard set of alerts based on best practices we have acquired in the last ten years of monitoring eMagiz models.
25
26 == 3. Alerting in eMagiz ==
27
28 Assessing the health of your systems is critical in a stable and robust integration solution.
29 Getting alerts when something deviates is crucial to guarantee a stable and robust integration solution.
30
31 First, we look at the standard set of alerts generated by eMagiz and explain them to you. Building on that, we will show where in eMagiz you can see the list of triggered alerts on your environment in the last two weeks.
32
33 === 3.1 Standard Alerting ===
34
35 * This list of alerts is predefined for all of our customer models
36 * This list cannot be altered or deleted by a user
37 * The list is generated based on a set of best practices acquired during the last ten years of monitoring eMagiz models
38 * You can view the list under Manage -> Triggers
39 * We will expand this functionality by offering the possibility of creating a dynamic trigger that is specific for a specific environment of your model
40 * All triggers have a time window on which they are triggered; most static alerts are based on a 10-minute time window.
41
42 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz--static-alerts-overview.png]]
43
44 As you can see in the list of alerts we generate for you, most of them should look familiar. Most of them probably look familiar to you, as they were also available in the current list of alerts. Some new additions on the list are related to API endpoints to give enhanced possibilities for monitoring your API endpoints in eMagiz.
45
46 === 3.2 Alerting Overview ===
47
48 When you navigate to Manage -> Alerting (-> Alerts), you will see all alerts that have been triggered in the last two weeks.
49
50 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz--triggered-alerts-overview.png]]
51
52 In this overview, you have various options to filter your results to get a sense of what is happening within your model in a specific environment.
53
54 == 4. Key takeaways ==
55
56 There are three areas in which you can configure alerting:
57
58 * Error Messages
59 * Measurement Data
60 * Missing Data
61
62 From eMagiz, we provide a standard set of alerts based on best practices we have acquired in the last ten years of monitoring eMagiz models.
63
64 == 5. Suggested Additional Readings ==
65
66 If you are interested in this topic and want more information, please read the help text provided by eMagiz and read the following microlearning on dynamic alerting.
67
68 * [[Dynamic alerting>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]]
69 * [[Setting up notifications>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Alerting.intermediate-alerting-setting-up-notifications-gen3||target="blank"]]
70
71 )))((({{toc/}}))){{/container}}
72 {{/container}}

Navigation

eMagiz
1.0.0