Why do I need to collect the debug-level log file? The Java agent by default logs the entries at the info level. Sometimes, the debug-level log files are necessary to investigate an experienced issue. Debug-level logging logs are more insightful entries that can be later used to identify the root cause of the experienced issue. There are two ways you can collect the agent log files at the desired logging level. From the AppDynamics controller UI. From the server, where the agent was installed. Collect the Java agent log files from the AppDynamics controller UI. Log into the controller UI. Select the problematic app. Open the 'Tiers & Nodes' dashboard. Select the problematic node. Select the 'Agents' tab. Scroll down to the 'Agent Operations' section and click on the 'Request Agent Log Files' button.  Set the logging level properties. Logger Name: com.singularity Logger Level: Debug Duration (minutes): at least 5 Click on the 'Request Agent Log Files' button to start the log files collection. If it is a test environment, please make sure to generate the load on the app during the log file collection. Collect the Java agent log files from the server, where the agent was installed. (optional) Delete the '/<java-agent-home>/<version>/logs/<node-name>/' directory. Edit the '/<java-agent-home>/<version>/conf/logging/log4j2.xml' file. Change the logging level as in the example below. <!-- to control the logging level of the agent log files, use the level attribute below. value="all|trace|debug|info|warn|error"--> <AsyncLogger name="com.singularity" level="debug" additivity="false">     <AppenderRef ref="Default"/>     <AppenderRef ref="RESTAppender"/> </AsyncLogger> Apply the load on the app (if it is a test environment) for at least 5 minutes. Zip the '/<java-agent-home>/<version>/logs/<node-name>/' directory. Revert the change. I hope this article was helpful. Feel free to ask in case of any questions. ... View more