Skip to content

Commit 2bf6159

Browse files
jeanbisuttitrask
andauthored
Update support/azure/azure-monitor/app-insights/telemetry/java-standalone-troubleshoot.md
Co-authored-by: Trask Stalnaker <[email protected]>
1 parent 85a7851 commit 2bf6159

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -242,7 +242,7 @@ Alternatively, you can try the following experimental feature: [Startup time imp
242242

243243
## Understand duplicated operation ID
244244

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).
245+
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).
246246

247247
The duplication may also come from incoming requests. To spot this second possibility:
248248
* Enable the capture of the `traceparent` header in the `applicationinsigths.json ` file

0 commit comments

Comments
 (0)