|
|
|
|
Configuration File
<TRAVERSE_HOME>/etc/log4j.conf
Restart These Components After Changing the Configuration File
Description
Different components of Traverse provide useful diagnostic and informative log messages. You can specify the amount of logged information by changing LOGLEVEL to one of the following parameters in the following table.
Log Message Detail Levels
LOGLEVEL |
Level of Detail |
|
Informational messages that highlight the progress of the application at a coarse-grained level. |
|
Designates potentially harmful situations. |
|
Designates error events that might still allow the application to continue running. |
|
Designates very severe error events that will presumably lead the application to abort. |
|
Additional detailed information that is useful for debugging an application. Do not enable debug messages unless asked to do so by Kaseya Support. |
By default, Traverse only logs messages into log files stored in the directory specified by the $LOGDIR variable. If you want to send logs to a UNIX syslog host at a central location or on same hosts, uncomment the following section:
#log4j.appender.SYSLOG = org.apache.log4j.net.SyslogAppender
#log4j.appender.SYSLOG.SyslogHost = localhost
#log4j.appender.SYSLOG.facility =
org.apache.log4j.net.SyslogAppender.LOG_LOCAL7
Then change localhost to the FQDN or IP address of the host to which you want to send the log messages. If you want the messages sent as a facility other than local7, change LOG_LOCAL7 to LOG_FACILITY where FACILITY is one of the facilities listed in the man page (man5) of syslogd.conf. Make sure to enter the facility name in upper case.