Skip to content

Commit afee190

Browse files
committed
Incorporatin feedback
1 parent 6b1b464 commit afee190

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/azure-monitor/app/distributed-tracing-telemetry-correlation.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -171,9 +171,7 @@ It's important to make sure the incoming and outgoing configurations are exactly
171171
172172
### Enable W3C distributed tracing support for web apps
173173
174-
This feature is in `Microsoft.ApplicationInsights.JavaScript`. Whether this feature is enabled by default is determined by which domain host the requests are sent to.
175-
176-
If requests are sent to the same domain host as the hosting page, this feature is enabled by default and uses the AI_AND_W3C setting (for example, the hosting page is `example.com` and the Ajax requests are sent to `example.com`). To disable it, use the [`distributedTracingMode` configuration field](./javascript-sdk-configuration.md#sdk-configuration). AI_AND_W3C is provided for backward compatibility with any legacy services instrumented by Application Insights.
174+
This feature is enabled by default for Javascript and the headers are automatically included when the hosting page domain is the same as the domain the requests are sent to (for example, the hosting page is `example.com` and the Ajax requests are sent to `example.com`). To change the distributed tracing mode, use the [`distributedTracingMode` configuration field](./javascript-sdk-configuration.md#sdk-configuration). AI_AND_W3C is provided by default for backward compatibility with any legacy services instrumented by Application Insights.
177175
178176
- **[npm-based setup](./javascript-sdk.md?tabs=npmpackage#get-started)**
179177
@@ -189,7 +187,7 @@ If requests are sent to the same domain host as the hosting page, this feature i
189187
distributedTracingMode: 2 // DistributedTracingModes.W3C
190188
```
191189
192-
If the XMLHttpRequest or Fetch Ajax requests are sent to a different domain host, including sub-domains, the correlation headers are not included by default. To enable this feature, set the [`enableCorsCorrelation` configuration field](./javascript-sdk-configuration.md#sdk-configuration) to `true`. If you set `enableCorsCorrelation` to `true`, all XMLHttpRequest and Fetch Ajax requests include the correlating headers. As a result, if the server that is being called does not support the `traceparent` header, the request may fail, depending on the browser / version. If the browser / version is unsupported, the browser won’t send the request.
190+
If the XMLHttpRequest or Fetch Ajax requests are sent to a different domain host, including sub-domains, the correlation headers are not included by default. To enable this feature, set the [`enableCorsCorrelation` configuration field](./javascript-sdk-configuration.md#sdk-configuration) to `true`. If you set `enableCorsCorrelation` to `true`, all XMLHttpRequest and Fetch Ajax requests include the correlation headers. As a result, if the application on the server that is being called doesn't support the `traceparent` header, the request may fail, depending on whether the browser / version can validate the request based on which headers the server will accept.
193191
194192
> [!IMPORTANT]
195193
> To see all configurations required to enable correlation, see the [JavaScript correlation documentation](./javascript.md#enable-distributed-tracing).

0 commit comments

Comments
 (0)