Skip to Content
Last modified by Erik Bakker on 2024/02/22 12:36
From version 4.1
edited by eMagiz
on 2022/05/05 09:56
Change comment: There is no comment for this version
To version 7.1
edited by eMagiz
on 2022/05/05 10:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,14 +1,6 @@
1 1  {{html wiki="true"}}
2 2  <div class="ez-academy">
3 3   <div class="ez-academy_body">
4 -
5 -
6 - <li class="doc-nav__item"><a href="../../docs/microlearning/advanced-advanced-monitoring-index" class="doc-nav__link">Home</a></li>
7 -
8 -
9 -
10 -
11 -
12 12  
13 13  <div class="doc">
14 14  
... ... @@ -15,7 +15,7 @@
15 15  
16 16  
17 17  = Interpreting wrapper.log on-premise =
18 -
10 +
19 19  There is a need to see runtime level logging in cases where it is unclear whether that specific runtime has started up or not. In eMagiz, you won't receive logging if the start-up fails because no established connection can send logging to eMagiz. When this particular runtime runs on-premises, you can see that specific logging on the runtime in the wrapper.log. In this microlearning, we will learn how to find the wrapper log and search within the wrapper log to find the corresponding error and subsequently analyze that error.
20 20  
21 21  Should you have any questions, please get in touch with academy@emagiz.com.
... ... @@ -24,9 +24,11 @@
24 24  * Required reading time: 5 minutes
25 25  
26 26  == 1. Prerequisites ==
19 +
27 27  * Advanced knowledge of the eMagiz platform
28 28  
29 29  == 2. Key concepts ==
23 +
30 30  This microlearning centers around interpreting the wrapper.log for an on-premise runtime
31 31  With a wrapper.log, we mean: A file that holds start-up and shut down information on a specific runtime
32 32  
... ... @@ -38,7 +38,6 @@
38 38  
39 39  
40 40  
41 -
42 42  == 3. Interpreting wrapper.log on-premise ==
43 43  
44 44  There is a need to see runtime level logging in cases where it is unclear whether that specific runtime has started up or not. In eMagiz, you won't receive logging if the start-up fails because no established connection can send logging to eMagiz. When this particular runtime runs on-premises, you can see that specific logging on the runtime in the wrapper.log. In this microlearning, we will learn how to find the wrapper log and search within the wrapper log to find the corresponding error and subsequently analyze that error.
... ... @@ -83,9 +83,9 @@
83 83  
84 84  As this is a more theoretical microlearning, we have no video for this.
85 85  
86 -
87 87  </div>
88 88  </main>
89 89  </div>
90 90  </div>
83 +
91 91  {{/html}}