Set the logging level for the amount of detail that you want to see: INFO, WARNING or DEBUG. The default is level is WARNING.

For maximum debugging information, set the logging level to DEBUG. Debug-level logs show the information that the Python Agent is sending to the proxy, which can be useful for debugging the agent.

For quick debugging, set the debugging configuration option to on. This causes debug-level logs to be written to both stderr and log files.

This is the behavior you can expect with various combinations of logging level and debug settings:

The various combinations of logging level and debug settings produce behavior as follows:

• level=info, debugging=off : Info-level logs are written to the log file
• level=warning, debugging=off : Warning-level logs are written to the log file
• level=debug, debugging=off : Debug-level logs are written to the log file
• level=info, debugging=on : Debug-level logs are written to the log file and to stderr
• level=warning, debugging=on : Debug-level logs are written to the log file and to stderr
• level=debug, debugging=on : Debug-level logs are written to the log file and to stderr

The Proxy logging level is separate and is not affected by the configuration settings of the Agent logging levels. Proxy logging level is "info" by default. Typically, you can redirect that output to a file if desired. In case if you wish to increase the logging level output, you must do so by starting the Proxy manually. First assign the new logging level within the Proxy's configuration file (proxy/conf/logging/log4j.xml) and then invoke the Proxy task.