Skip to Content
Last modified by Erik Bakker on 2024/02/22 12:35
From version 9.2
edited by Erik Bakker
on 2024/02/22 12:35
Change comment: Update document after refactoring.
To version 4.1
edited by Erik Bakker
on 2022/06/23 15:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -advanced-active-monitoring-determining-cause-of-log-entry
1 +Determining cause of log entry
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.eMagiz Academy.Microlearnings.Legacy Functionality.WebHome
1 +Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.WebHome
Content
... ... @@ -1,8 +1,4 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -{{error}}
3 -Note that the functionality mentioned in this microlearning will become obsolete when migrating to the 3rd generation runtime.
4 -{{/error}}
5 -
6 6  When something goes wrong within the process, you want to determine what caused the error to be raised. In earlier microlearnings, we learned how to determine the cause of error messages. Now, we shift our focus to the log entries. In eMagiz, errors can show up in the dashboard and the log entries. For this microlearning, we will look at the log entries and see how we can use that information to look at the flow to determine what part of the flow is causing the error.
7 7  
8 8  Should you have any questions, please get in touch with academy@emagiz.com.
... ... @@ -45,12 +45,20 @@
45 45  
46 46  [[image:Main.Images.Microlearning.WebHome@advanced-active-monitoring-determining-cause-of-log-entry--current-faulty-check.png]]
47 47  
48 -== 4. Key takeaways ==
44 +== 4. Assignment ==
49 49  
46 +Search for problems in the log and see if you can find out what caused these problems. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
47 +
48 +== 5. Key takeaways ==
49 +
50 50  * The log entry shows which flow has raised the error
51 51  * You need to read the log entry to interpret on which component the error is raised
52 52  * With the information from the log entry, you can analyze the flow starting at the component that raised the error and move back in the process step by step
53 53  
54 -== 5. Suggested Additional Readings ==
54 +== 6. Suggested Additional Readings ==
55 55  
56 -If you are interested in this topic and want more information, please read the release notes provided by eMagiz.)))((({{toc/}}))){{/container}}{{/container}}
56 +If you are interested in this topic and want more information, please read the release notes provided by eMagiz.
57 +
58 +== 7. Silent demonstration video ==
59 +
60 +As this is a more theoretical microlearning, we have no video that accompanies this microlearning.)))((({{toc/}}))){{/container}}{{/container}}