How to enable logging in the Denodo Monitor
You can translate the document:
Overview
In this document we will explain how to configure the Denodo Monitor to enable additional logs for getting information about the Denodo Monitor process itself. This document describes the instructions to follow to enable those internal logs of the Denodo Monitor.
Depending on the Denodo Monitor that you are using, you need to follow different instructions.
These instructions are valid for Denodo 9, Denodo 8 20220728 and newer versions.
NOTE: These logs can be very verbose and use a lot of disk space. Make sure that enough space is available in the destination hard drive and to disable these logs once they are no longer needed.
Standalone Denodo Monitor
- Add the property monitor.internal.log.active=true in the <DENODO_MONITOR_HOME>/conf/ConfigurationParameters.properties file.
- Generate a new log4j2.xml file under the <DENODO_MONITOR_HOME>/conf folder with the following content:
|
<?xml version="1.0" encoding="UTF-8"?> <Configuration>
<Appenders>
<RollingFile name="FILEOUT" fileName="../logs/denodo-monitor.log" filePattern="denodo-monitor.log.%i"> <Policies> <SizeBasedTriggeringPolicy size="10 MB" /> </Policies> <DefaultRolloverStrategy max="7" /> <PatternLayout pattern="%-4r [%t] %-5p %d{yyyy-MM-dd'T'HH:mm:ss.SSS} %c %x - %m%n"/> </RollingFile>
<Console name="STDOUT" target="SYSTEM_OUT"> <PatternLayout pattern="%-4r [%t] %-5p %d{yyyy-MM-dd'T'HH:mm:ss.SSS} - %m%n"/> </Console>
</Appenders>
<Loggers>
<logger name="com.denodo.monitor" level="INFO" additivity="false"> <appender-ref ref="FILEOUT" /> </logger>
<!-- Prints more information about the denodo-monitor in the output. For example, information about connections, shutdown hooks, InterruptedException... --> <logger name="com.denodo.monitor.startstopinfo" level="INFO" additivity="true"> <appender-ref ref="STDOUT" /> </logger>
<logger name="org.apache.logging.log4j" level="ERROR" additivity="false"> <appender-ref ref="FILEOUT" /> </logger>
<Root level="INFO"> <AppenderRef ref="FILEOUT" /> <AppenderRef ref="STDOUT" /> </Root>
</Loggers>
</Configuration> |
- The Denodo Monitor can be started as usual. Logs for the Denodo Monitor itself will be generated in the <DENODO_MONITOR_HOME>/logs/denodo-monitor.log file.
Solution Manager Denodo Monitor
- Add the property monitor.internal.log.active=true in the <SOLUTION_MANAGER_HOME>/conf/solution-manager/denodo-monitor/ConfigurationParametersGeneral.template file.
- Generate a new log4j2.xml file under the <SOLUTION_MANAGER_HOME>/conf/solution-manager/denodo-monitor folder with the following content:
|
<?xml version="1.0" encoding="UTF-8"?>
<Configuration>
<Appenders>
<RollingFile name="FILEOUT" fileName="monitor-internal-logs/denodo-monitor.log" filePattern="denodo-monitor.log.%i"> <Policies> <SizeBasedTriggeringPolicy size="10 MB" /> </Policies> <DefaultRolloverStrategy max="7" /> <PatternLayout pattern="%-4r [%t] %-5p %d{yyyy-MM-dd'T'HH:mm:ss.SSS} %c %x - %m%n"/> </RollingFile>
<Console name="STDOUT" target="SYSTEM_OUT"> <PatternLayout pattern="%-4r [%t] %-5p %d{yyyy-MM-dd'T'HH:mm:ss.SSS} - %m%n"/> </Console>
</Appenders>
<Loggers>
<logger name="com.denodo.monitor" level="INFO" additivity="false"> <appender-ref ref="FILEOUT" /> </logger>
<!-- Prints more information about the denodo-monitor in the output. For example, information about connections, shutdown hooks, InterruptedException... --> <logger name="com.denodo.monitor.startstopinfo" level="INFO" additivity="true"> <appender-ref ref="STDOUT" /> </logger>
<logger name="org.apache.logging.log4j" level="ERROR" additivity="false"> <appender-ref ref="FILEOUT" /> </logger>
<Root level="INFO"> <AppenderRef ref="FILEOUT" /> <AppenderRef ref="STDOUT" /> </Root>
</Loggers>
</Configuration> |
- Once the monitoring is started from the Solution Manager, you can check the denodo-monitor.log file in the monitoring folder for every environment (<SOLUTION_MANAGER_HOME>/resources/solution-manager-monitor/work/<workspace-environment-cluster-server>/monitor-internal-logs)
References
The information provided in the Denodo Knowledge Base is intended to assist our users in advanced uses of Denodo. Please note that the results from the application of processes and configurations detailed in these documents may vary depending on your specific environment. Use them at your own discretion.
For an official guide of supported features, please refer to the User Manuals. For questions on critical systems or complex environments we recommend you to contact your Denodo Customer Success Manager.
