Azure Application Insights多项目.NET Core 2调试遥测显示异常排查

Let’s break down the possible missing configurations that could be causing this odd split in telemetry visibility:

• Visual Studio Debug Telemetry Filtering
  By default, Visual Studio’s Application Insights debugger tool might be set to only show telemetry from the actively selected project. Check the dropdown in the Application Insights window (usually found under View > Other Windows > Application Insights Search) and make sure it’s set to All Projects instead of just your Web API project. Sometimes the tool auto-focuses on the project you started debugging first, hiding telemetry from others.

• Console Project Telemetry Initialization & Flush Behavior
  Console apps don’t have the automatic telemetry pipeline setup that ASP.NET Core Web APIs do. If your console projects aren’t explicitly flushing telemetry, the data might be sent directly to Azure but not captured in the VS debug session. Ensure you’re calling telemetryClient.Flush(); and adding a small delay (like Task.Delay(1000).Wait();) after sending telemetry, especially when the app exits. Also, verify that you’re initializing the TelemetryConfiguration correctly for console apps—using the same instrumentation key as the Web API, and not overriding any settings that would bypass the local debug listener.

• Sampling Configuration Mismatches
  It’s possible your Web API has sampling enabled that’s filtering out telemetry in the Azure Portal, while local debugging in VS ignores sampling. Conversely, console apps might have sampling turned off, sending all data to Azure. Check your appsettings.json (for Web API) and code configuration (for console apps) for SamplingSettings. Ensure that local debugging isn’t overriding sampling in a way that hides data from Azure, and that Azure isn’t sampling out the Web API’s telemetry entirely.

• Visual Studio Application Insights Tooling & NuGet Versions
  Visual Studio 2017 15.5.2 is a fairly old release, and the Application Insights tooling for console apps was still improving back then. Try updating the Microsoft.ApplicationInsights related NuGet packages in all projects to the latest compatible version for .NET Core 2.0. Additionally, check if there are any Visual Studio updates available—even a minor patch might fix the telemetry capture inconsistency for console projects.

• Environment-Specific Instrumentation Key Checks
  Double-check that all projects are using the exact same instrumentation key across their debug configurations. Web APIs often rely on appsettings.Development.json for local settings, while console apps might have the key hardcoded or in a different config file. Ensure that when debugging locally, none of the projects are pointing to a different AI resource by accident.

• Telemetry Channel Configuration Differences
  ASP.NET Core Web APIs typically use ServerTelemetryChannel which handles batching and retries, while console apps might default to InMemoryChannel. Visual Studio’s debug listener might only capture telemetry sent through the server channel. Try configuring your console apps to use ServerTelemetryChannel to match the Web API’s setup, which could make their telemetry show up in the VS debug session.

内容的提问来源于stack exchange，提问作者Ravi Chinni