More about troubleshooting logs

Author: trask

articles/azure-monitor/app/java-standalone-troubleshoot.md

@@ -12,10 +12,17 @@ In this article, we cover some of the common issues that you might face while in
 
 ## Check the self-diagnostic log file
 
-By default, Application Insights Java 3.x produces a log file named `applicationinsights.log` in the same directory that holds the `applicationinsights-agent-3.2.2.jar` file.
+By default, Application Insights Java 3.x produces a log file named `applicationinsights.log` in the same directory
+that holds the `applicationinsights-agent-3.2.7.jar` file.
 
 This log file is the first place to check for hints to any issues you might be experiencing.
 
+If no log file is generated, check that your Java application has write permission to the directory that holds the
+`applicationinsights-agent-3.2.7.jar` file.
+
+If still no log file is generated, check the stdout log from your Java application. Application Insights Java 3.x
+should log any errors to stdout that would prevent it from logging to its normal location.
+
 ## JVM fails to start
 
 If the JVM fails to start with "Error opening zip file or JAR manifest missing",