Changes for page Log Alerting
Last modified by Bouke Reitsma on 2024/12/04 11:28
From 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
To 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
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -10,27 +10,26 @@ 10 10 11 11 == 2. Key concepts == 12 12 13 -This microlearning focuses on creating and customizing the erroralerts 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 log alerts that are existing in each of the environment of your model (i.e., Testing-Acceptance-Production). 14 14 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 15 +* There are three checks that eMagiz currently provides that will raise an alert from the log messages: 16 +** log message 17 +** log level 19 19 ** Runtime check 20 -* Recipients are defined on each erroralert trigger.19 +* Recipients are defined on each log alert trigger. 21 21 22 -== 3. ErrorAlerting ==23 - Erroralerting refers to the configuration of triggers that will generate an alert, as well as send you a notification, whenevererrormessages with certain conditions are raised. This functionality is most likely relevant when an alert needs to be generated whenever a specificerrormessagewith certain characteristics (e.g., a particularheadervalue or a particularexceptionmessage) is raised and that alert needs to be sent to a different set of recipients.21 +== 3. log Alerting == 22 +Log alerting refers to the configuration of triggers that will generate an alert, as well as send you a notification, whenever log entries with certain conditions are raised. This functionality is most likely relevant when an alert needs to be generated whenever a specific log entry with certain characteristics (e.g., a particular log level or a particular log message) is raised and that alert needs to be sent to a different set of recipients. 24 24 25 25 [[image:Main.Images.Microlearning.WebHome@novice-alerting-error-alerts-overview.png]] 26 26 27 -Similar to the queuealerting, you can find the overview of theerroralerting by navigating to Manage->Alerting->Triggers, then under the "Errors" tab you will find all of theerroralert 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 newerrortrigger, you can press the "Add" button. Otherwise, if you want to edit an existingerroralert trigger, you can click the green edit button on the right side of each trigger.26 +Similar to the error alerting, you can find the overview of the log alerting by navigating to Manage->Alerting->Triggers, then under the "Logs" tab you will find all of the log 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 log trigger, you can press the "Add" button. Otherwise, if you want to edit an existing log alert trigger, you can click the green edit button on the right side of each trigger. 28 28 29 -eMagiz currently provides four checks that will raise an alert from theerrormessages, namely, by evaluating theMessageheader,Exceptionclass, Exception message, and the Runtime where theerrormessageis raised. In the following sections, we will discuss how you can create anerrortrigger and tune its trigger checks to match your needs.28 +eMagiz currently provides three checks that will raise an alert from the log entries, namely, by evaluating the log message, Log level, and the Runtime where the log entry is raised. In the following sections, we will discuss how you can create an log trigger and tune its trigger checks to match your needs. 30 30 31 -{{info}}When setting up the erroralert triggers, these considerations apply:32 -* An alert will be generated for an errormessageonly if all checks and conditions specified in a trigger apply.33 -* If all checksina triggeris set to "Ignore", then you will get an alert for everyerrormessage thatis raised.30 +{{info}}When setting up the log alert triggers, these considerations apply: 31 +* An alert will be generated for an log entry only if all checks and conditions specified in a trigger apply. 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" 34 34 {{/info}} 35 35 36 36 === 3.1 Evaluate message header ===