Changes for page Log Alerting
Last modified by Bouke Reitsma on 2024/12/04 11:28
From version 3.1
edited by Bouke Reitsma
on 2024/12/04 10:39
on 2024/12/04 10:39
Change comment:
There is no comment for this version
To version 4.1
edited by Bouke Reitsma
on 2024/12/04 10:49
on 2024/12/04 10:49
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -32,37 +32,27 @@ 32 32 * If the Evaluate log message setting is set to "Ignore", then you will get an alert for **every** log message for the specified runtimes, the "Ignore" setting can only be applied for Log Level "Error" 33 33 {{/info}} 34 34 35 -=== 3.1 Evaluate message header===35 +=== 3.1 Evaluate log message === 36 36 37 -This check evaluates whether an alert should be generated when an errormessageis raised based on theheadercontained in the message.37 +This check evaluates whether an alert should be generated when an log entry is raised based on the contents of the log message. 38 38 39 39 [[image:Main.Images.Microlearning.WebHome@novice-alerting-error-alerts-evaluate-message-header.png]] 40 40 41 -If you set it to "Ignore", then message headerswill not be evaluated when deciding whether to raise an alert. If set to "By Condition," then you can specify whatheadernameto evaluate and define conditions such as whether it equals, does not equal, contains, or does not containa specificvaluetoresult inan alert.41 +If you set it to "Ignore", then log message will not be evaluated when deciding whether to raise an alert. If set to "By Condition," then you can specify what value to evaluate and define conditions such as whether it equals, does not equal, contains, or does not contain within the log message. 42 42 43 -=== 3.2 Evaluatexception class===43 +=== 3.2 Log level === 44 44 45 -This check evaluates whether an alert should be generated based on the e xceptionclass of the errormessagewhen it is raised.45 +This check evaluates whether an alert should be generated based on the log level of the log entry when it is raised. There are three types of log level based on the risk/severity of the log, namely info, warning, and error. For each trigger you can specify the log level, you can also combine levels for example, warning and error levels. 46 46 47 47 [[image:Main.Images.Microlearning.WebHome@novice-alerting-error-alerts-evaluate-exception-class.png]] 48 48 49 - Ifyou set it to "Ignore", then the exception class will not be evaluated when determining whether an alert should be raised.If set to "By Condition", then youcanspecify whatexception class toevaluateand defineconditions suchas whether it equals, does not equal,contains,or does not contain a specific value to result in an alert.49 +=== 3.3 Runtime check === 50 50 51 - ===3.3Evaluate exceptionmessage===51 +This check evaluates whether an alert should be generated when an log entry is raised from which runtime in the environment. 52 52 53 -This check evaluates whether an alert should be generated based on both the first and last exception message of the error message when it is raised. 54 - 55 -[[image:Main.Images.Microlearning.WebHome@novice-alerting-error-alerts-evaluate-exception-message.png]] 56 - 57 -If you set it to "Ignore", then the exception message will not be evaluated when determining whether an alert should be raised. If set to "By Condition," then you can specify a string to check in both the first and last exception messages, and define conditions like equals, not equals, contains, or does not contain to result in an alert. 58 - 59 -=== 3.4 Runtime check === 60 - 61 -This check evaluates whether an alert should be generated when an error message is raised from which runtime in the environment. 62 - 63 63 [[image:Main.Images.Microlearning.WebHome@novice-alerting-error-alerts-runtime-check.png]] 64 64 65 -If you set it to "Ignore", then which runtime where the error occured will not be evaluated when determining whether an alert should be raised. If set to "By Condition", then you can specify which runtime where the errormessageoccured to result in an alert.55 +If you set it to "Ignore", then which runtime where the error occured will not be evaluated when determining whether an alert should be raised. If set to "By Condition", then you can specify which runtime where the log entry occured to result in an alert. 66 66 67 67 === 3.5 Instruction === 68 68 ... ... @@ -70,12 +70,12 @@ 70 70 71 71 [[image:Main.Images.Microlearning.WebHome@novice-alerting-error-alerts-instructions.png]] 72 72 73 -Lastly, upon saving, these settings will apply immediately, putting the new erroralert trigger into effect. Next to that, on this page, you can also find the "Notifications" tab that allows you to configure which recipients that you want to receive the notifications from the error alerting. If you want to learn more about this notifications and how to configure it, please refer to this [[microlearning>>Main.eMagiz Academy.Microlearnings.Intermediate Level.Alerting.intermediate-alerting-setting-up-notifications-gen3||target="blank"]].63 +Lastly, upon saving, these settings will apply immediately, putting the new log alert trigger into effect. Next to that, on this page, you can also find the "Notifications" tab that allows you to configure which recipients that you want to receive the notifications from the error alerting. If you want to learn more about this notifications and how to configure it, please refer to this [[microlearning>>Main.eMagiz Academy.Microlearnings.Intermediate Level.Alerting.intermediate-alerting-setting-up-notifications-gen3||target="blank"]]. 74 74 75 75 == 4. Key takeaways == 76 76 77 -* eMagiz allows users to create and customize erroralerts by defining triggers that will raise alerts and send notifications when error messages with specific conditions occur.78 -* eMagiz provides four checks forerroralerts: messageheader,exceptionclass,exception message, and runtime. These checks can be configured to evaluate conditions such as "equals," "not equals," "contains," or "does not contain" to determine if an alert should be triggered.67 +* eMagiz allows users to create and customize log alerts by defining triggers that will raise alerts and send notifications when error messages with specific conditions occur. 68 +* eMagiz provides three checks for log alerts: log message, log level, and runtime. These checks can be configured to evaluate conditions such as "equals," "not equals," "contains," or "does not contain" to determine if an alert should be triggered. 79 79 * Alerts are generated only if all specified checks in a trigger are met. Users can also configure recipients for error alert notifications, ensuring messages reach the appropriate stakeholders. 80 80 81 81 == 5. Suggested Additional Readings ==