Update support/azure/azure-monitor/app-insights/telemetry/java-standalone-troubleshoot.md

jeanbisutti · trask · web-flow · commit 85a78511a6c1 · 2025-01-06T18:36:16.000+01:00
Co-authored-by: Trask Stalnaker &lt;trask.stalnaker@gmail.com&gt;
diff --git a/support/azure/azure-monitor/app-insights/telemetry/java-standalone-troubleshoot.md b/support/azure/azure-monitor/app-insights/telemetry/java-standalone-troubleshoot.md
@@ -245,7 +245,7 @@ Alternatively, you can try the following experimental feature: [Startup time imp
 The application logic can result in the operation ID being reused by multiple telemetry data, as shown by [this example](/azure/azure-monitor/app/distributed-trace-data#example).
 
 The duplication may also come from incoming requests. To spot this second possibility:
-* Enable the capture of the trace parent headers in the  `applicationinsigths.json ` file
+* Enable the capture of the `traceparent` header in the  `applicationinsigths.json ` file
 ```json
 {
   "preview": {

Original file line number	Diff line number	Diff line change
`@@ -245,7 +245,7 @@ Alternatively, you can try the following experimental feature: [Startup time imp`
`245`	`245`	`The application logic can result in the operation ID being reused by multiple telemetry data, as shown by [this example](/azure/azure-monitor/app/distributed-trace-data#example).`
`246`	`246`
`247`	`247`	`The duplication may also come from incoming requests. To spot this second possibility:`
`248`		-* Enable the capture of the trace parent headers in the `applicationinsigths.json ` file
	`248`	+* Enable the capture of the `traceparent` header in the `applicationinsigths.json ` file
`249`	`249`	```json
`250`	`250`	`{`
`251`	`251`	`"preview": {`