LSF Version 7.3 - Administering Platform LSF

Reports Administration
642 Administering Platform LSF
Dynamically change the log level of your loader controller log file
Use the loader controller client tool to dynamically change the log level of your plc
log file if it does not cover enough detail, or covers too much, to suit your needs.
If you restart the
plc service, the log level of your plc log file will be set back to the
default level. To retain your new log level, change the level of your
plc log file as
described in Change the log level of your log files on page 642.
1 Launch the loader controller client tool with the -l option.
❖ In UNIX, run $PERF_TOP/bin/plcclient.sh -l log_level.
❖ In Windows, run $PERF_TOP\bin\plcclient -l log_level.
In decreasing level of detail, the log levels are
ALL (for all messages), TRACE,
DEBUG, INFO, WARN, ERROR, FATAL, and OFF (for no messages).
Dynamically change the log level of your data loader log files
Use the loader controller client tool to dynamically change the log level of your
individual data loader log files if they do not cover enough detail, or cover too
much, to suit your needs.
If you restart the
plc service, the log level of your data loader log files will be set
back to the default level. To retain your new log level, change the level of your data
loader log files as described in Change the log level of your log files on page 642.
1 If you are using the default configuration file, launch the loader controller client
tool with the
-n and -l options.
❖ In UNIX, run $PERF_TOP/version/bin/plcclient.sh
-n
data_loader_name -l log_level.
❖ In Windows, run %PERF_TOP%\version\bin\plcclient
-n
data_loader_name -l log_level.
Refer to Loader controller on page 638 for a list of the data loader names.
In decreasing level of detail, the log levels are
ALL (for all messages), TRACE,
DEBUG, INFO, WARN, ERROR, FATAL, and OFF (for no messages).
Change the log level of your log files
Change the log level of your log files if they do not cover enough detail, or cover too
much, to suit your needs.
1 Edit the log4j.properties file, located in the reports configuration directory
(
PERF_CONFDIR).
2 Navigate to the section representing the service you want to change, or to the
default loader configuration if you want to change the log level of the data
loaders, and look for the log4j.logger.com.platform.perf. variable.