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 14.1
edited by Erik Bakker
on 2023/09/28 21:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,11 +1,12 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 +{{error}}
3 +Note that the functionality mentioned in this microlearning will become obsolete when migrating to the 3rd generation runtime.
4 +{{/error}}
5 +
2 2  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.
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.
... ... @@ -45,24 +45,12 @@
45 45  
46 46  One way to do so would be to stop the runtime and delete the data folder without deleting the h2 folder. That would initiate a clean restart of the runtime to alleviate the problems. In case of structural issues, you should dive into the logging and analyze the issues in more detail.
47 47  
47 +== 45. Key takeaways ==
48 48  
49 -
50 -== 4. Assignment ==
51 -
52 -Run your own Academy project on your laptop (on-premise), so you can experiment a bit with analyzing the karaf.log on-premise. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
53 -
54 -== 5. Key takeaways ==
55 -
56 -* The karaf.log can be found within the folder called log under the folder data
49 +* The wrapper.log can be found within the folder called log under the folder data
57 57  * You can search the log with the help of tools such as Notepad++
58 58  * By looking at the timestamp in the eMagiz Manage Log, you can run a focused search
59 59  
53 +== 5. Suggested Additional Readings ==
60 60  
61 -
62 -== 6. Suggested Additional Readings ==
63 -
64 -No suggested additional readings for this microlearning.
65 -
66 -== 7. Silent demonstration video ==
67 -
68 -As this is a more theoretical microlearning, we have no video for this.)))((({{toc/}}))){{/container}}{{/container}}
55 +No suggested additional readings for this microlearning.)))((({{toc/}}))){{/container}}{{/container}}