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 2.1
edited by Bouke Reitsma
on 2024/12/04 09:57
on 2024/12/04 09:57
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -10,26 +10,27 @@ 10 10 11 11 == 2. Key concepts == 12 12 13 -This microlearning focuses on creating and customizing the logalerts that are existing in each of the environment of your model (i.e., Testing-Acceptance-Production).13 +This microlearning focuses on creating and customizing the error alerts that are existing in each of the environment of your model (i.e., Testing-Acceptance-Production). 14 14 15 -* There are three checks that eMagiz currently provides that will raise an alert from the log messages: 16 -** log message 17 -** log level 15 +* There are four checks that eMagiz currently provides that will raise an alert from the error messages: 16 +** Message header 17 +** Exception class 18 +** Exception message 18 18 ** Runtime check 19 -* Recipients are defined on each logalert trigger.20 +* Recipients are defined on each error alert trigger. 20 20 21 -== 3. logAlerting ==22 - Logalerting refers to the configuration of triggers that will generate an alert, as well as send you a notification, wheneverlogentries with certain conditions are raised. This functionality is most likely relevant when an alert needs to be generated whenever a specificlogentrywith certain characteristics (e.g., a particularlog level or a particularlogmessage) is raised and that alert needs to be sent to a different set of recipients.22 +== 3. Error Alerting == 23 +Error alerting refers to the configuration of triggers that will generate an alert, as well as send you a notification, whenever error messages with certain conditions are raised. This functionality is most likely relevant when an alert needs to be generated whenever a specific error message with certain characteristics (e.g., a particular header value or a particular exception message) is raised and that alert needs to be sent to a different set of recipients. 23 23 24 24 [[image:Main.Images.Microlearning.WebHome@novice-alerting-error-alerts-overview.png]] 25 25 26 -Similar to the e rroralerting, you can find the overview of thelogalerting by navigating to Manage->Alerting->Triggers, then under the "Logs" tab you will find all of thelogalert triggers, if you have created them already, for the environment that you are working with at the moment (i.e., Testing, Acceptance, Production). To create a newlogtrigger, you can press the "Add" button. Otherwise, if you want to edit an existinglogalert trigger, you can click the green edit button on the right side of each trigger.27 +Similar to the queue alerting, you can find the overview of the error alerting by navigating to Manage->Alerting->Triggers, then under the "Errors" tab you will find all of the error alert triggers, if you have created them already, for the environment that you are working with at the moment (i.e., Testing, Acceptance, Production). To create a new error trigger, you can press the "Add" button. Otherwise, if you want to edit an existing error alert trigger, you can click the green edit button on the right side of each trigger. 27 27 28 -eMagiz currently provides threechecks that will raise an alert from thelogentries, namely, by evaluating thelog message,Loglevel, and the Runtime where thelogentryis raised. In the following sections, we will discuss how you can create anlogtrigger and tune its trigger checks to match your needs.29 +eMagiz currently provides four checks that will raise an alert from the error messages, namely, by evaluating the Message header, Exception class, Exception message, and the Runtime where the error message is raised. In the following sections, we will discuss how you can create an error trigger and tune its trigger checks to match your needs. 29 29 30 -{{info}}When setting up the logalert triggers, these considerations apply:31 -* An alert will be generated for an logentryonly if all checks and conditions specified in a trigger apply.32 -* If the Evaluatelogmessagesetting is set to "Ignore", then you will get an alert for**every**logmessageforthespecified runtimes,the "Ignore" setting can only be appliedfor Log Level "Error"31 +{{info}}When setting up the error alert triggers, these considerations apply: 32 +* An alert will be generated for an error message only if all checks and conditions specified in a trigger apply. 33 +* If all checks in a trigger is set to "Ignore", then you will get an alert for every error message that is raised. 33 33 {{/info}} 34 34 35 35 === 3.1 Evaluate message header ===