You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2020. It is now read-only.
Built-in Azure Service Fabric's reverse proxy is access through localhost. Due to this logic (line about localhost) AI SDK doesn't do correlation:
<Add Type="Microsoft.ApplicationInsights.DependencyCollector.DependencyTrackingTelemetryModule, Microsoft.AI.DependencyCollector">
<ExcludeComponentCorrelationHttpHeadersOnDomains>
<!--
Requests to the following hostnames will not be modified by adding correlation headers.
Add entries here to exclude additional hostnames.
NOTE: this configuration will be lost upon NuGet upgrade.
-->
<Add>core.windows.net</Add>
<Add>core.chinacloudapi.cn</Add>
<Add>core.cloudapi.de</Add>
<Add>core.usgovcloudapi.net</Add>
<Add>localhost</Add>
<Add>127.0.0.1</Add>
</ExcludeComponentCorrelationHttpHeadersOnDomains>
<IncludeDiagnosticSourceActivities>
<Add>Microsoft.Azure.EventHubs</Add>
<Add>Microsoft.Azure.ServiceBus</Add>
</IncludeDiagnosticSourceActivities>
</Add>
According to @lmolkova this logic isn't required anymore. Let's remove it?
The text was updated successfully, but these errors were encountered:
Do NOT do this workaround if you have Microsoft.ApplicationInsights.DependencyCollector 2.6.0 or previous versions and run Azure Storage Emulator on localhost! It results in issue sending requests to storage.
Workaround
ASP.NET (classic) - ApplicationInsights.Web SDK from 2.7.0-beta1 to 2.9.0-beta2
Users can enable correlation on localhost by removing
<Add>localhost</Add>
<Add>127.0.0.1</Add>
AspNetCore (ApplicaitonInsights.AspNetCore from 2.4.0-beta1 to 2.6-beta2) users can do
Built-in Azure Service Fabric's reverse proxy is access through localhost. Due to this logic (line about localhost) AI SDK doesn't do correlation:
According to @lmolkova this logic isn't required anymore. Let's remove it?
The text was updated successfully, but these errors were encountered: