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 9.2
edited by Erik Bakker
on 2022/06/23 15:50
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Interpreting wrapper.log on-premise
1 +advanced-advanced-monitoring-interpreting-wrapper-log-on-premise
Content
... ... @@ -1,4 +1,6 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 += Interpreting wrapper.log on-premise =
3 +
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]].
advanced-advanced-monitoring-interpreting-wrapper-log-on-premise--wrapper-log-location.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ebakker
Size
... ... @@ -1,0 +1,1 @@
1 +35.8 KB
Content