Skip to Content
Last modified by Erik Bakker on 2024/02/22 12:36
From version 11.1
edited by Erik Bakker
on 2022/06/23 15:52
Change comment: Deleted image "advanced-advanced-monitoring-interpreting-wrapper-log-on-premise--wrapper-log-location.png"
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
Content
... ... @@ -3,9 +3,6 @@
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 -* Last update: November 15st, 2021
7 -* Required reading time: 5 minutes
8 -
9 9  == 1. Prerequisites ==
10 10  
11 11  * Advanced knowledge of the eMagiz platform
... ... @@ -21,8 +21,6 @@
21 21  * Shutdown information on JVM level
22 22  * Errors on start-up or shutdown
23 23  
24 -
25 -
26 26  == 3. Interpreting wrapper.log on-premise ==
27 27  
28 28  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.