Skip to content

Commit e548dc1

Browse files
committed
Move thread dump to github wiki
1 parent 0cef411 commit e548dc1

File tree

1 file changed

+1
-11
lines changed

1 file changed

+1
-11
lines changed

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

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ you can also set the connectiong string by loading it from a file.
7373
}
7474
```
7575

76-
`connection-string-file.txt` only contains the connection string:
76+
`connection-string-file.txt` can be an absolute or relative path to the the agent jar location. It only contains the connection string:
7777

7878
```
7979
InstrumentationKey=...;IngestionEndpoint=...
@@ -596,16 +596,6 @@ and the console, corresponding to this configuration:
596596
Starting from version 3.0.2, you can also set the self-diagnostics `level` using the environment variable `APPLICATIONINSIGHTS_SELF_DIAGNOSTICS_LEVEL`
597597
(which will then take precedence over self-diagnostics level specified in the json configuration).
598598

599-
600-
## Thread dump
601-
602-
We use thread dump to troubleshoot Java Codeless Agent's startup performance.
603-
If you experience that the agent startup takes longer than usual, you can submit the thread dump to us and we can help you investigate the cause of the slowness.
604-
605-
If you use a JVM arg `-Dapplicationinsights.debug.startupProfiling=true`, it will automatically generate a thread dump file under the default temp folder `applicationinsights/stacktrace.txt`.
606-
607-
`applicationinsights.log` will have the file path. It has something like `Writing startup profiler to C:\Users\${USER_NAME}\AppData\Local\Temp\applicationinsights\stacktrace.txt`.
608-
609599
## An example
610600

611601
This is just an example to show what a configuration file looks like with multiple components.

0 commit comments

Comments
 (0)