Skip to Content
Last modified by Erik Bakker on 2024/02/22 12:36
From version 9.2
edited by Erik Bakker
on 2022/06/23 15:50
Change comment: Update document after refactoring.
To version 12.1
edited by Erik Bakker
on 2023/01/23 11:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -advanced-advanced-monitoring-interpreting-wrapper-log-on-premise
1 +Interpreting wrapper.log on-premise
Content
... ... @@ -1,13 +1,8 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -= Interpreting wrapper.log on-premise =
3 -
4 4  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.
5 5  
6 6  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
8 -* Last update: November 15st, 2021
9 -* Required reading time: 5 minutes
10 -
11 11  == 1. Prerequisites ==
12 12  
13 13  * Advanced knowledge of the eMagiz platform
... ... @@ -23,8 +23,6 @@
23 23  * Shutdown information on JVM level
24 24  * Errors on start-up or shutdown
25 25  
26 -
27 -
28 28  == 3. Interpreting wrapper.log on-premise ==
29 29  
30 30  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.
advanced-advanced-monitoring-interpreting-wrapper-log-on-premise--wrapper-log-location.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ebakker
Size
... ... @@ -1,1 +1,0 @@
1 -35.8 KB
Content