Merge pull request #284505 from AaronMaxwell/aaronmax-disable-corr

Info to disable telemetry correlation

Author: prmerger-automator[bot]

articles/azure-monitor/app/asp-net-core.md

@@ -854,6 +854,10 @@ When you add Application Insights Telemetry to a Visual Studio ASP.NET Core temp
             }
     ```
 
+### How can I disable telemetry correlation?
+
+To disable telemetry correlation in code, see `<ExcludeComponentCorrelationHttpHeadersOnDomains>` in [Application Insights for console applications](/previous-versions/azure/azure-monitor/app/console).
+
 ## Troubleshooting
 
 See the dedicated [troubleshooting article](/troubleshoot/azure/azure-monitor/app-insights/asp-net-troubleshoot-no-data).

articles/azure-monitor/app/asp-net.md

@@ -533,6 +533,10 @@ The following pieces of code are automatically added:
             }
     ```
 
+### How can I disable telemetry correlation?
+
+To disable telemetry correlation in configuration, see `<ExcludeComponentCorrelationHttpHeadersOnDomains>` in [Application Insights for console applications](/previous-versions/azure/azure-monitor/app/console).
+
 ## Troubleshooting
 
 See the dedicated [troubleshooting article](/troubleshoot/azure/azure-monitor/app-insights/asp-net-troubleshoot-no-data).

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

@@ -909,6 +909,18 @@ Starting from version 3.0.2, you can also set the self-diagnostics `level` by us
 
 Starting from version 3.0.3, you can also set the self-diagnostics file location by using the environment variable `APPLICATIONINSIGHTS_SELF_DIAGNOSTICS_FILE_PATH`. It then takes precedence over the self-diagnostics file path specified in the JSON configuration.
 
+## Telemetry correlation
+
+Telemetry correlation is enabled by default, but you may disable it in configuration.
+
+```json
+{
+  "preview": {
+    "disablePropagation": true
+  }
+}
+```
+
 ## An example
 
 This example shows what a configuration file looks like with multiple components. Configure specific options based on your needs.

articles/azure-monitor/app/nodejs.md

@@ -459,6 +459,12 @@ These properties are client specific, so you can configure `appInsights.defaultC
 | correlationIdRetryIntervalMs    | The time to wait before retrying to retrieve the ID for cross-component correlation. (Default is `30000`.)     |
 | correlationHeaderExcludedDomains| A list of domains to exclude from cross-component correlation header injection. (Default. See [Config.ts](https://github.com/Microsoft/ApplicationInsights-node.js/blob/develop/Library/Config.ts).)|
 
+## Frequently asked questions
+
+#### How can I disable telemetry correlation?
+
+To disable telemetry correlation, use the `correlationHeaderExcludedDomains` property in configuration. For more information, see [ApplicationInsights-node.js](https://github.com/microsoft/ApplicationInsights-node.js#configuration).
+
 ## Troubleshooting
 
 For troubleshooting information, including "no data" scenarios and customizing logs, see [Troubleshoot Application Insights monitoring of Node.js apps and services](/troubleshoot/azure/azure-monitor/app-insights/troubleshoot-app-insights-nodejs).