Skip to Content

Wiki source code of eMagiz SFTP Connection guide

Version 1.1 by eMagiz on 2022/06/02 12:13
Show last authors
1 {{html wiki="true"}}
2 <div class="ez-academy">
3 <div class="ez-academy_body">
4
5 <div class="doc">
6
7
8
9 = Determining the origin of log entries =
10
11 In this microlearning, we will focus on how you can quickly and easily determine the origin of log entries. In other words, what caused the logging.
12
13 Should you have any questions, please contact academy@emagiz.com.
14
15 * Last update: July 22th, 2021
16 * Required reading time: 5 minutes
17
18 == 1. Prerequisites ==
19
20 * Basic knowledge of the eMagiz platform
21 * Understanding of Monitoring concept
22 * One or more log entries raised in the last two weeks within the context of your (Academy) project
23
24 == 2. Key concepts ==
25
26 This microlearning centers around determining the origin of log entries.
27 By origin, in this context, we mean: Identifying which flow wrote an entry to the log that might be in need of analysis.
28
29 * Determining in which flow a log entry is raised can be done with the help of the Manage phase in eMagiz.
30 * In the Manage phase you have an option called Monitoring. In this overview, you will see all logging that is relevant without your project.
31 * This overview allows you to filter on various elements, such as runtime, type, and timestamp. This way you can conduct a more focused search.
32 * Double-clicking on a log entry provides you with the relevant details
33 * Note that log entries are not shown in full when they exceed a certain size so takes this into account when logging
34 * When you know the flow and the details you have determined the origin of the log entry
35
36
37
38 == 3. Determining the origin of log entries ==
39
40 You can determine the origin of a log entry with a two-step approach:
41
42 1. Search in the Monitoring overview for log entries
43 2. Select a specific log entry for further analysis
44
45 === 3.1 Monitoring overview Manage ===
46
47 To see and analyze the log entries you need to navigate to Manage -> Monitoring. This overview shows all log entries within your project that have been written to the log in the last fourteen days (assuming you did adhere to the fair use policy). Within this overview, you have the ability to search on various options such as runtime, type, and timestamp.
48
49 <p align="center">[[image:intermediate-active-monitoring-determining-origin-of-log-entry--manage-monitoring-unfiltered.png||]]</p>
50
51 <p align="center">[[image:intermediate-active-monitoring-determining-origin-of-log-entry--manage-monitoring-filtered.png||]]</p>
52
53 === 3.2 Select a specific log entry for further analysis ===
54
55 After you have filtered the log entries to your liking you can select a specific log entry by double-clicking on the log entry. By doing so a pop-up will be presented in which the details of the log entry are written. On this details page, the flow and message are the most relevant from a user perspective.
56
57 <p align="center">[[image:intermediate-active-monitoring-determining-origin-of-log-entry--manage-monitoring-log-entry-details.png||]]</p>
58
59 Note that some log entries are grouped as they appeared in short proximity after each other and have to do with the same logging.
60
61 <p align="center">[[image:intermediate-active-monitoring-determining-origin-of-log-entry--manage-monitoring-log-entry-details-grouped.png||]]</p>
62
63 ===== Practice =====
64
65 == 4. Assignment ==
66
67 Determine the origin of at least five log entries that have been raised within your (Academy) project in the last two weeks. If your project has no log entries be creative in messing up stuff to create a log entry for which you can then determine the origin.
68
69 == 5. Key takeaways ==
70
71 * Determining in which flow a log entry is raised can be done with the help of the Manage phase in eMagiz.
72 * In the Manage phase you have an option called Monitoring. In this overview, you will see all logging that is relevant without your project.
73 * This overview allows you to filter on various elements, such as runtime, type, and timestamp. This way you can conduct a more focused search.
74 * Double-clicking on a log entry provides you with the relevant details
75 * Note that log entries are not shown in full when they exceed a certain size so takes this into account when logging
76 * When you know the flow and the details you have determined the origin of the log entry
77
78
79
80 == 6. Suggested Additional Readings ==
81
82 If you are interested in this topic and want more information on it please read the help text provided by eMagiz when executing these actions.
83
84 == 7. Silent demonstration video ==
85
86 This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
87
88 <iframe width="1280" height="720" src="../../vid/microlearning/intermediate-active-monitoring-determining-origin-of-log-entry.mp4" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
89
90 </div>
91
92 </div>
93 </div>
94
95 {{/html}}