Alerting in eMagiz

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.

36

37

=== 3.1 Standard Static Alerting ===

38

39

* This list of alerts is predefined for all of our customer models

40

* This list cannot be altered or deleted by a user

41

* The list is generated based on a set of best practices acquired during the last ten years of monitoring eMagiz models

42

* You can view the list under Manage -> Triggers

43

* We will expand this functionality by offering the possibility of creating a dynamic trigger that is specific for a specific environment of your model

44

* All triggers have a time window on which they are triggered; most static alerts are based on a 10-minute time window.

45

46

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz--static-alerts-overview.png]]

47

48

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.

49

50

=== 3.2 Alerting Overview ===

51

52

When you navigate to Manage -> Alerting (-> Alerts), you will see all alerts that have been triggered in the last two weeks.

53

54

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz--triggered-alerts-overview.png]]

55

56

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.

== 4. Assignment ==

The assignment is simple this time. Navigate to the trigger (Manage -> Alerting -> Triggers) overview in eMagiz and analyze the static triggers eMagiz generates by default.

61

This assignment can be completed with the help of an associated Mendix project linked to the (Academy) project that you created/used in the previous assignment.

62

63

== 5. Key takeaways ==

64

65

There are three areas in which you can configure alerting:

* Error Messages

* Measurement Data

* Missing Data

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.

72

73

== 6. Suggested Additional Readings ==

74

75

If you are interested in this topic and want more information, please read the help text provided by eMagiz.

76

77

== 7. Silent demonstration video ==

78

79

This video demonstrates how you could have handled the assignment and gives context to what you have just learned.

TBA

)))((({{toc/}}))){{/container}}

84

Wiki source code of Alerting in eMagiz

Navigation

version	line-number	content
38.1	1	{{container}}
	2	{{container layoutStyle="columns"}}(((
	3
	4	{{warning}}
	5	Please note that this microlearning is for the new monitoring stack only.
	6	{{/warning}}
	7
	8	Assessing the health of your systems is critical in a stable and robust integration solution.
	9	Getting alerts when something deviates is crucial to guarantee a stable and robust integration solution.
	10
	11	In this microlearning, we will educate you on Alerting within the Manage phase of eMagiz.
	12
	13	== 1. Prerequisites ==
	14
	15	* Basic knowledge of the eMagiz platform
	16
	17	== 2. Key concepts ==
	18
	19	This microlearning centers around setting up the alerting in eMagiz.
	20	With alerting, we mean: Configuring thresholds that raise an alert when the point is passed.
	21
	22	There are three areas in which alerting is configured for you by eMagiz:
	23
	24	* Error Messages
	25	* Measurement Data
	26	* Missing Data
	27
	28	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.
	29
	30	== 3. Alerting in eMagiz ==
	31
	32	Assessing the health of your systems is critical in a stable and robust integration solution.
	33	Getting alerts when something deviates is crucial to guarantee a stable and robust integration solution.
	34
	35	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.
	36
	37	=== 3.1 Standard Static Alerting ===
	38
	39	* This list of alerts is predefined for all of our customer models
	40	* This list cannot be altered or deleted by a user
	41	* The list is generated based on a set of best practices acquired during the last ten years of monitoring eMagiz models
	42	* You can view the list under Manage -> Triggers
	43	* We will expand this functionality by offering the possibility of creating a dynamic trigger that is specific for a specific environment of your model
	44	* All triggers have a time window on which they are triggered; most static alerts are based on a 10-minute time window.
	45
	46	[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz--static-alerts-overview.png]]
	47
	48	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.
	49
	50	=== 3.2 Alerting Overview ===
	51
	52	When you navigate to Manage -> Alerting (-> Alerts), you will see all alerts that have been triggered in the last two weeks.
	53
	54	[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-manage-alerting-in-emagiz--triggered-alerts-overview.png]]
	55
	56	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.
	57
	58	== 4. Assignment ==
	59
	60	The assignment is simple this time. Navigate to the trigger (Manage -> Alerting -> Triggers) overview in eMagiz and analyze the static triggers eMagiz generates by default.
	61	This assignment can be completed with the help of an associated Mendix project linked to the (Academy) project that you created/used in the previous assignment.
	62
	63	== 5. Key takeaways ==
	64
	65	There are three areas in which you can configure alerting:
	66
	67	* Error Messages
	68	* Measurement Data
	69	* Missing Data
	70
	71	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.
	72
	73	== 6. Suggested Additional Readings ==
	74
	75	If you are interested in this topic and want more information, please read the help text provided by eMagiz.
	76
	77	== 7. Silent demonstration video ==
	78
	79	This video demonstrates how you could have handled the assignment and gives context to what you have just learned.
	80
	81	TBA
	82
	83	)))((({{toc/}}))){{/container}}
	84	{{/container}}