Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 20:30
From version 2.1
edited by eMagiz
on 2022/06/02 12:13
Change comment: There is no comment for this version
To version 8.1
edited by eMagiz
on 2022/06/02 12:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,95 +1,61 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
1 +{{container}}
2 +{{container layoutStyle="columns"}}
3 +(((
4 += How to connect with the eMagiz SFTP Service =
4 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 -
6 +In this microlearning, we will provide short guide that will help eMagiz users how to connect to the eMagiz SFTP service. Allthough this is a regular SFTP service, there are some specific steps involved to allow an optimal configuration of the integration.
7 +
13 13  Should you have any questions, please contact academy@emagiz.com.
14 14  
15 -* Last update: July 22th, 2021
10 +* Last update: June 2nd, 2022
16 16  * Required reading time: 5 minutes
17 17  
18 18  == 1. Prerequisites ==
19 19  
20 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 -
16 +* Understanding of the way in which an SFTP file pickup or drop is configured in eMagiz
17 +* Reviewed microlearning :: TO ADD
18 +
19 +
24 24  == 2. Key concepts ==
21 +By the eMagiz SFTP, we mean: A specific SFTP offered by the eMagiz platform on which you can securely store and read messages. Considerations when connecting to the eMagiz SFTP
25 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.
23 +* Did you read the connect guide and made sure that all requirements are met?
24 +* Did you use the store component made available in the eMagiz store to set up the connection?
25 +* Did you verify that the indicator for temporary file name is set to false?
28 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 35  
28 +== 3. How to steps ==
36 36  
30 +=== 3.1 Obtain an SFTP User account
31 +Make sure to get the access credentials from eMagiz Support. Ensure to obtain access credentials for all connected systems/applications that need to send or received files from the SFTP service. Every application team will get a specific user, and the eMagiz model will get it's own user. In this way, the data is securely provided to the ecosystem of the eMagiz model. For instance, in case there are 4 applications involved that need to get or send data to the SFTP service there will be 5 SFTP service users
37 37  
38 -== 3. Determining the origin of log entries ==
33 +=== 3.2 Create (agreed) folder structure
39 39  
40 -You can determine the origin of a log entry with a two-step approach:
41 41  
42 -1. Search in the Monitoring overview for log entries
43 -2. Select a specific log entry for further analysis
36 +=== 3.3 Dispatch folder structure fixed to eMagiz Support
44 44  
45 -=== 3.1 Monitoring overview Manage ===
46 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 48  
49 -<p align="center">[[image:intermediate-active-monitoring-determining-origin-of-log-entry--manage-monitoring-unfiltered.png||]]</p>
50 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 65  == 4. Assignment ==
66 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.
43 +Take a moment to locate the Store component for eMagiz.
68 68  
69 69  == 5. Key takeaways ==
70 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
47 +* The eMagiz SFTP Service requires use of a specific Store component
48 +* Please contact eMagiz Support to ensure the right configuration is created including the proper file paths inside the SFTP user folder
49 +* Ensure to update eMagiz Support whenever the file path changes
77 77  
78 78  
79 -
80 80  == 6. Suggested Additional Readings ==
81 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.
54 +None available
83 83  
84 84  == 7. Silent demonstration video ==
85 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}}
58 +None available
59 +)))
60 +((({{toc/}}))){{/container}}
61 +{{/container}}